1. Sivaprakash BKR
  2. PowerBuilder
  3. Tuesday, 23 May 2023 05:53 AM UTC

Hello,

Is the IDE used to compile PB 2022 R2 different from PB 2022 R1?
Do we have to test in full, if we upgrade from PB 2022 B 1900 to R2? 

Happiness Always
BKR Sivaprakash

 

Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 23 May 2023 16:22 PM UTC
  2. PowerBuilder
  3. # 1

Hi Sivaprakash,

Don't quite understand your question/concern.

First of all, the PB IDE and runtime have been separated for quite some time now.  So single PB IDE version could target 2022 R1, 2022 R2, and even minor builds of R1 or R2.  You just select from dropdown and compile.  So I don't see any significant risk that you upgrade to 2022 R2 because you could always recompile your app for R1 if problems.

With that said, anytime you roll out new app runtime version (not IDE update) into production environment it is important to do comprehensive testing before.  Maintenance releases are less risky, but for a revision (e.g. R2) and especially major new versions you should test.  As John said, it's your choice but definitely not a best practice.

As far as what has changed between R1 and R2, please refer to the new features guide: https://docs.appeon.com/pb/whats_new/index.html

Best regards,
Armeen

Comment
  1. Sivaprakash BKR
  2. Wednesday, 24 May 2023 04:55 AM UTC
Somewhere in this forum I read Chris saying that PB 2022 R2 is compiled with higher version of VS from PB 2022 R1. Also, he used to say that upgrade from PB 2019 R3 to PB 2022 needs thorough checking. Mixing up these two, I have a doubt whether 2022 R2 also needs that amount of checking while upgrading from 2022 R1.
  1. Helpful
  1. Armeen Mazda @Appeon
  2. Wednesday, 24 May 2023 15:26 PM UTC
The upgrade to 2022 has introduced some more significant changes: https://docs.appeon.com/pb/upgrading_pb_apps/UpgradingPowerBuilderApplications-UpgradingfromPowerBuilder2021orearlier.html

Going from 2022 R1 to R2 is not so significant (basically removal of Inet object): https://docs.appeon.com/pb/upgrading_pb_apps/UpgradingPowerBuilderApplications-UpgradingfromPowerBuilder2022orearlier.html

I recommend don't get caught up with technical details Chris says. Please follow the upgrade guide usually it is correct about real impact to your project (excluding bugs of course).
  1. Helpful
There are no comments made yet.
John Fauss Accepted Answer Pending Moderation
  1. Tuesday, 23 May 2023 11:44 AM UTC
  2. PowerBuilder
  3. # 2

Do you HAVE to test?

No, nobody’s forcing you to do anything.

SHOULD you test? That’s an entirely different matter. Why would you not test?

Please keep in mind that PB 2022 R2 is a beta release, not a General Availability release. The product may change between beta and GA. 

Comment
  1. Andreas Mykonios
  2. Tuesday, 23 May 2023 12:54 PM UTC
Hi John.

I believe that the most important part of your answer is that the product may change between Beta and GA.

Andreas.
  1. Helpful
  1. Armeen Mazda @Appeon
  2. Wednesday, 24 May 2023 15:27 PM UTC
Hi Andreas, Between Beta and GA the underlying product does not change. We basically fixing bugs. But to your point, comprehensive testing should be done on the final release because even bug fixes can introduce regression issues or change in behaviors.
  1. Helpful
There are no comments made yet.
Andreas Mykonios Accepted Answer Pending Moderation
  1. Tuesday, 23 May 2023 07:14 AM UTC
  2. PowerBuilder
  3. # 3

Hi.

If you ask because you want to install the 2022 R2 on your production pc, before going on take a look at the following answer by Chris Pollach https://community.appeon.com/index.php/qna/q-a/my-initial-findings-on-the-new-powerbuilder-2022-r2-beta#reply-40125.

Andreas.

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.