Andreas & Armeen,

Thank you both for your quick and detailed response. Majority of our clients are running client-server but we do have quite a few clients running on web as well. Our goal (next 12-18 months) is to move all our applications to version PB/PS 2022 R3. In the meantime, we want to continue with PB 2019 R2 build 2353 and PS 2020 build 2323 so we can support our clients until we have production version of 2022 R3.

Regards,

Vinod

Hi Vinod, 

Adding to great answers by Andreas, I wanted to elaborate on some details that is specific to your situation of using legacy PowerServer version.

1) If you stay with PB 2019 R2, you have no support for client/server apps and no support for the IDE itself.  But the PS 2020 is still supported.  So as long as your issue is not a bug in the IDE or issue with client/server app, staying with PB 2019 R2 still gets you support until PS 2020 EOL.

2) Yes, you can still use PS 2020 with PB 2019 R3, but I would recommend considering upgrading to a newer build of PS 2020.  Many fixes have been made in later builds of PS 2020.... you are on a 4 year old build of PS 2020.  In fact, I would go as far to say if you aren't deploying any client/server apps, the higher priority would be to upgrade your PS 2020 build than the IDE.  Here are the fixes we made: https://www.appeon.com/standardsupport/bugfixes?contents=&product=PowerServer+2020+or+older+%28Obsolete%29&category=&version=2020&build=  

3) The IDE will not affect the architecture and deployment of PS 2020.  The architecture and deployment of PS 2020 is driven by the PS version not PB version.  But as Andreas pointed out, if you are doing client/server apps also besides PS then yes for client/server there is some difference in deployment due to the separation of the client/server runtime from the IDE.

4) Same answer as #3.

Best regards,
Armeen

Hi.

You can continue to use PB 2019 R2, but you can't expect to get support for that version. About your questions:

Continue with PB 2019 R2 until the migration to PB 2022 R3 is complete (approx. 12-18 months). What are the repercussions of continuing to run on PB 2019 R2 Build 2353 & PS 2020 Build 2323 (for web builds)?

You won't be able to get support. In my opinion this is a serious problem.

If we migrate to PB 2019 R3 and do web builds, will the web application still run on PS 2020 Build (2323)?

You should use the appropriate version of powerserver. Last release of PB 2019 R3 is 2803 which also provides PowerServer. Be aware that previous versions of PowerServer are already EOL... To be able to get support for PowerServer 2020 you should be running on PowerServer 2020 build 2323, 2703, 2758, 2779 or 2803 (or to the equivallent PowerServer for PB).

Is PB 2019 R3 version and PB 2019 R2 Build 2353 version similar in architecture? Will web end users find it a smooth transition when we upgrade to PB 2019 R3 web builds? (example, IWARunner, downloaded files etc.)

There was a big change in PB 2019 R3, as in this version the IDE was separated from the runtime. This affects the way native application should be deployed. You can read the following chapter from documentation: Decoupling Runtime and IDE - - What's New (appeon.com). PowerClient deployment was introduced (PowerClient deployment - - What's New (appeon.com)). Those changes were the most important in my humble opinion. There are some improvements related to PowerServer (Improvements - - Release Bulletin for PowerBuilder (appeon.com), Improvements - - Release Bulletin for PowerBuilder (appeon.com)).

For other new features you can check New Features - - What's New (appeon.com).

If we have to move to PB 2019 R3, which build should we move to that is compatible with PS 2020 Build 2353?

I guess this should be one of 2779 or 2803. The main change in those is that the later one uses a different webbrowser control. So it depends on what your application is doing... Both are pretty stable.

Andreas.