1. Gimmy Susan
  2. PowerBuilder
  3. Monday, 5 September 2022 22:19 PM UTC

Hello everybody.
I just installed version 2022.
As you can see from the image, the new version does not see the old runtimes.
Did I do something wrong?

 

Thanks in advance for the reply

 

Gimmy Susan Accepted Answer Pending Moderation
  1. Tuesday, 6 September 2022 22:18 PM UTC
  2. PowerBuilder
  3. # 1

Hi Chris.
It was a pleasure to help you.
(I can brag about helping a code boss )   tongue-out
My bad English and my fair Italian are always at your disposal.

G.

Comment
  1. Chris Pollach @Appeon
  2. Tuesday, 6 September 2022 23:57 PM UTC
Ottimo! :-)
  1. Helpful
There are no comments made yet.
Gimmy Susan Accepted Answer Pending Moderation
  1. Tuesday, 6 September 2022 06:39 AM UTC
  2. PowerBuilder
  3. # 2

Hi Chris
As you can see from my previous answer this thing represents a disappointment.

As with PB2021 (it was compatible with 2019r3 runtimes) I expected the same thing for 2022.

I can't believe we're back to having to have an IDE for each version.

Not all of our customers are willing to invest for the version change (Is my company weird? I don't think so).
This is a big problem for developers because they have tons of IDEs installed on their computers. Without bearing in mind that every IDE has its pre-requisites.


Bad very bad.

This is my 2 cents opinion.

Comment
  1. Chris Pollach @Appeon
  2. Tuesday, 6 September 2022 11:06 AM UTC
Hi Gimmy;

I wish that I had better news but Mike said it best in that we'll need to keep one Appeon PB IDE installation per major release going forward. This is due to technical dependencies in the PB architectures used "under the hood".

BTW: thanks again many years back for helping me create the Italian version of the STD Framework.

Regards ... Chris
  1. Helpful 1
  1. mike S
  2. Tuesday, 6 September 2022 13:11 PM UTC
still - this is so much better than before when every BUILD had its own ide update requirement. Now at least we have will have just 1 IDE to worry with for 2022 R1/R2/R3 and all builds between. Also, it is not a hard requirement that every major release will require a new IDE, just that you should expect that it will.



fwiw, with the way the runtime version is set (at the IDE level and not the application level), having multiple IDEs actually works out fine for me.



  1. Helpful
There are no comments made yet.
Gimmy Susan Accepted Answer Pending Moderation
  1. Tuesday, 6 September 2022 06:00 AM UTC
  2. PowerBuilder
  3. # 3

Hi Mike

 

My expectation is that Powerbuilder will (finally) work like Visual Studio with .NET. Each version of visual studio is compatible with previous versions of .NET

This is the REAL utility of splitting IDE from RUNTIME

(This is my 2 cent opinion)

Comment
There are no comments made yet.
mike S Accepted Answer Pending Moderation
  1. Monday, 5 September 2022 23:48 PM UTC
  2. PowerBuilder
  3. # 4

I believe that your expectation for this going forward should be that all runtimes within a major release will work only in the IDE of that major release.  So you will typically need to keep an IDE for each major version if you need one or more runtimes of that major version.

Comment
  1. Armeen Mazda @Appeon
  2. Tuesday, 6 September 2022 00:44 AM UTC
Mike is exactly right!
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 5 September 2022 22:59 PM UTC
  2. PowerBuilder
  3. # 5

Hi Gimmy;

   That's correct .... You should see this restriction in the "what's new" section of the PB Help. The reason for this is because the PB2022's IDE & Runtime uses a much newer version of the C++ compiler - which is not backwards compatible to older Appeon PB versions.

Regards ... Chris 

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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.