1. Marc Wietscher
  2. PowerBuilder
  3. Thursday, 14 December 2017 09:46 AM UTC

Good morning,

we have several products developed with PB2017, which in future might be build on different releases of the same PB version, especially when it comes to maintaining legacy versions of our products. So we would like to know, if it will be possible to install more than one release of an appeon PB version on a machine to develop and maintain these products.

I know we could install each release to a different directory, but how to handle the app paths in registry? And how to deploy this to our customers who might have installed more than one of our products?

Currently we are embedding an msi created with the PowerBuilder runtime packager into our installation, so I think there is no chance to install PB runtimes into different directories on customer machines.

Best solution was, if appeon renames all PB dlls to eg. pbxxx172.dll for R2.


Thank you in advance for any advice


Ronnie Po Accepted Answer Pending Moderation
  1. Friday, 15 December 2017 19:00 PM UTC
  2. PowerBuilder
  3. # 1

Hello Marc and Eric,

One option would be:

For each deployed application, install all runtime files - the EXE, all required DLLs, OCX, etc. within the same directory as the given application. If two programs are created with the same version of PB, then you would end up installing duplicates of certain runtime files, but you would not have to install separately any shared runtime files and you would not have to deal with application path settings.

For example, your applications, including all required runtime files, would reside within:

C:\Program Files (x86)\Program 1\

C:\Program Files (x86)\Program 2\

C:\Program Files (x86(\Program 3\


There are no comments made yet.
Eric Freudenberg Accepted Answer Pending Moderation
  1. Friday, 15 December 2017 08:51 AM UTC
  2. PowerBuilder
  3. # 2

Good Morning,

thanks for the answers, but what Marc means is this:
We have several products that are simultaneously installed on one machine and communicate with each other via interfaces. Some of these products have been developed with different PowerBuilder releases, requiring different PBDKs (PowerBuilder Development / (Client-)Runtime Kit). Here is an example of the problem with future PB releases until 2019.

Fictitious situation on end-user PC May 2019:
Program 1: created with PowerBuilder 17 R1 (PB17DK R1) => our release 2017-12
Program 2: created with PowerBuilder 17 R2 (PB17DK R2) => our release 2018-02
Program 3: created with PowerBuilder 18 R1 (PB18DK R1) => our release 2019-02

This situation shows the view of the end-user PC in May 2019. All three programs are simultaneously installed on the machine.
If the programs use a common PBDK with which they were not built, there are various problems.

Now our questions:
Q1: How are the PBDKs installed?
Q2: Is the "C:\Program Files (x86)\Appeon\Shared\PowerBuilder" directory simply overwritten or use Appeon different versions?
Q3: Can PBDK-libraries (DLL's / OCX) simply be delivered as files or must the PBDK be installed on the machine by an installer?

Thank you in advance for any advice.


There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 15 December 2017 04:18 AM UTC
  2. PowerBuilder
  3. # 3

Hi Marc;

   Was able to confirm with Engineering that they will not be renaming the PBxxxx170.dll files for the PB 2017R2 release. My best suggestion is to make sure that you are using online licensing and install each PB version (Rx or MRx release) on separate VM's for each Application that requires a specific PB build.

Regards ... Chris

There are no comments made yet.
Roland Smith Accepted Answer Pending Moderation
  1. Thursday, 14 December 2017 13:18 PM UTC
  2. PowerBuilder
  3. # 4

I don't think registry settings for the IDE are going to be an issue. The most prominent of the registry settings are the database profiles and the source control settings for the workspaces which you would want to be the same anyway.

I had to keep separate copies of 11 and 11.2 and didn't have any issues.

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.