1. Cecilia Jiménez Bedoya
  2. PowerBuilder
  3. Friday, 10 November 2017 12:30 PM UTC

Hi,

Is it possible migrate a PB12.5 .NET proyect to PB2017?. The 12.5.net workspace extension is pbwx and PB2017 do not open it.

Roland Smith Accepted Answer Pending Moderation
  1. Friday, 10 November 2017 19:16 PM UTC
  2. PowerBuilder
  3. # 1

Your non-visual objects and DataWindows will likely be able to be imported manually but the windows and other visual objects will have to be redone by hand.

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 10 November 2017 14:25 PM UTC
  2. PowerBuilder
  3. # 2

HI Cecilia;

     Unfortunately, PB.Net has been EOL'ed and there is no direct replacement. As Roland well pointed out, PB 2017 is based on the PB 12.6 "Classic" IDE edition not the PB.Net IDE. Thus, PB 2017 will only work with classic workspaces & targets from previous PB based classic App's. You can see the official response on the Appeon website in the PB 2017 FAQ section and the question "What IDE will I be using to develop apps? about PB.Net.

    That being said, the only migration path that could save some or most of your PowerScript code in PB.Net (depending on the features you used), would be to manually transpose the reusable components and code into PB 2017 (ie Copy/Paste). Unfortunately, this could be a vary laborious process.

Regards ... Chris

 

Comment
There are no comments made yet.
Roland Smith Accepted Answer Pending Moderation
  1. Friday, 10 November 2017 13:21 PM UTC
  2. PowerBuilder
  3. # 3

PB.Net is a completely different environment which isn't supported anymore. PB 2017 only supports 'PowerBuilder Classic'.

Comment
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.