Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved Appeon PB with Visual Studio

  1. How-to
0
Votes
Undo
  1. John Brown
    John Brown
  2. PowerBuilder
  3. Monday, 21 November 2022 16:19 PM UTC

All -

Been doing PB development for 27 years ... never worked with in conjunction with Visual Studio.

My company is upgrading from Visual Studio 2010 to 2022.  I've been tasked with testing to make sure there are issues.

But I don't even know what I'm looking for ... I looked through the external DLLs, I searched for OLE items ( this is difficult to do ).

 

Any suggestions on what to look for?

 

Follow-up question : When PB compiles, how does it use the external, non-PB dlls - for example, custom written ones?  Those wouldn't need to be modified, correct?  

 

 

Thanks all,

John

RibbonBarCategoryItem visible property
Themes and unnecessary scrollbars
Responses (3)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 21 November 2022 16:44 PM UTC
  2. PowerBuilder
  3. # 1

Hi John;

  Up until PB2021, the PB IDE & runtime were done using VS C++ 2010. In PB 2022, Appeon started using VS C++ 2019. So if your calling external DLLs, there could be issues when using Window "Handles". Only thorough regression testing might uncover these. The key here would be to switch from using the "uLong" data type for handles over to the new "LongPTR" data type. However depending on how the external DLL(s) were written, this may not be necessary.

HTH

Regards ... Chris

Comment
There are no comments made yet.
John Brown
John Brown Accepted Answer Pending Moderation
  1. Monday, 21 November 2022 17:00 PM UTC
  2. PowerBuilder
  3. # 2

 

 

Chris - Thanks!

I failed to specify version - we are using PB2017 r3.

 

To clarify, there shouldn't be an issue unless we chose to migrate to a newer version of PB, am I correct in that understanding?

 

I don't even have Visual Studio on my machine.  I do all the coding and builds ( we use PowerGen ).

 

Thanks again!

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 21 November 2022 17:15 PM UTC
Correct ... PB 2017, 2019 & 2021 were still built using VS C++ 2010.
  1. Helpful 1
There are no comments made yet.
John Brown
John Brown Accepted Answer Pending Moderation
  1. Monday, 21 November 2022 17:30 PM UTC
  2. PowerBuilder
  3. # 3

"The key here would be to switch from using the "uLong" data type for handles over to the new "LongPTR" data type."

Is that in the external DLL logic?  Or in the PB code?  This stuff is all new to me ...LOL

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 21 November 2022 18:07 PM UTC
That's PowerScript John
  1. Helpful 1
John Brown
  1. John Brown
  2. Monday, 21 November 2022 18:11 PM UTC
Thanks, Chris - I wasn't sure. Might just be the apps I've worked on, but never seen anyone use uLong etc. I'll assume it means "unsigned" ... Thanks for all the guidance. Since we're on an older version of PB and the libraries are older, I'm assuming there won't be an issue. At least, I'm hoping.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.