1. Thomas Polak
  2. PowerBuilder
  3. Thursday, 31 October 2019 14:45 PM UTC

Our present deployment has a modular approach where each module is deployed as an exe.   The deployments presently are built in PowerBuilder 12.5. Each of these modules\exes have their respective PBDs residing in the same folder in a citrix environment.  

We have migrated one of the "modules" to PowerBuilder 2017 and will be deploying that shortly.  From what is understood is the 12.5 apps can coexist in the same folder as the PowerBuilder 2017 app. Meaning the runtime files are separate and each exe will use accordingly. 

But here is the question,  once we move to PowerBuilder 2019 and compile an app or some set of these module exe(s) will they be able to coexist in the same folder as the 12.5 versions and PowerBuilder 2017 versions?

Note:  We are aware the runtime are different for each version of PowerBuilder, but what about the common files between each runtime.

This was an inherited deployment standard from years ago and multiple vendors creating the modules, so it would be difficult to change. 

The skinny, can we have PowerBuilder 2017 built apps in the same folder as PowerBuilder 2019 built apps?

Roland Smith Accepted Answer Pending Moderation
  1. Thursday, 31 October 2019 15:02 PM UTC
  2. PowerBuilder
  3. # 1

The common files that don't have the PB version in them are compatible between versions. Many of them are provided by Microsoft.

Comment
  1. Thomas Polak
  2. Thursday, 31 October 2019 15:26 PM UTC
Thank you Roland. Is there any concern with developing PB 2017 apps and PB 2019 apps on the same development box?
  1. Helpful
  1. Roland Smith
  2. Thursday, 31 October 2019 15:47 PM UTC
There shouldn't be any problem with developing 2017 and 2019 on the same machine. You can't run both at the same time.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 31 October 2019 18:39 PM UTC
  2. PowerBuilder
  3. # 2

Hi Thomas;

 This can be a tricky question to answer ...

1) Are the PBXXXnnn.dll files OK in the same folder between "minor" PB releases ... NO

2) Are the PBXXXnnn.dll files OK in the same folder between "major" PB releases ... YES

3) Are the LIBxxxxxx.dll files OK in the same folder ... NO *

4) Are the MSVCxxxx.dll files OK in the same folder ... NO *

5) Is the NTWxxxxxx.dll file OK in the same folder ... NO *

6) Are the TP15xxxxx.dll files OK in the same folder ... NO +

7) Are the WRxxxxx.dll files OK in the same folder ... NO +

8) Are the XERxxxx.dll files OK in the same folder ... NO +

9) Is the ZLib.dll file OK in the same folder ... NO *

10) Are PBD's from the same App but, different PB compiles OK in the same folder ... NO

* Note: As long as these files come from the higher PB build - they should work with the lower PB run-times.

+ Note: Not an issue if these PB features are not used.

HTH

regards ... Chris

 

 

 

Comment
  1. Roland Smith
  2. Thursday, 31 October 2019 21:03 PM UTC
I'm wondering, how is the GZip decompression implemented? I may need to have that capability for a customer using 11.5. Is it using ZLIB? Bruce said at the conference it was 7Zip.
  1. Helpful
  1. Chris Pollach @Appeon
  2. Thursday, 31 October 2019 21:11 PM UTC
Hi Roland;

Its ZLib. You can see the ZLib.dll in the PB "Shared" folder.

Regards ... Chris
  1. Helpful
  1. Miguel Leeuwe
  2. Friday, 1 November 2019 03:17 AM UTC
I can confirm that richtext will stop working in at least one of the installed apps.
  1. Helpful
There are no comments made yet.
Olan Knight Accepted Answer Pending Moderation
  1. Thursday, 31 October 2019 22:51 PM UTC
  2. PowerBuilder
  3. # 3

Thomas, I am curious as to why you would not want to keep the PB2019 files in a separate folder from the PB12.5 files just as a  matter of principle?

Note: I am not being snarky, I really want to know!


Thank,

Olan

 

Comment
  1. Thomas Polak
  2. Monday, 4 November 2019 15:06 PM UTC
Olan, No worries on the curiosity. The system has been in place for decades and the way it was architected is each 'module' was a separate exe and all the executables reside in the same folder. There is a primary vendor who produced 40+ modules and a secondary vendor (us) who produced another 40 or so. The primary vendor has chosen to remain on PB12.5 while our corporate governance has mandated migration to the latest PB. In order to change the architecture would take an act of God. :-) Hence, it is what it is and all the exes (modules) will be comingled.
  1. Helpful
  1. Olan Knight
  2. Friday, 15 November 2019 21:18 PM UTC
Thank you, Thomas!
  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.