Hi Raymond;

  The installation of the PB runtime files location is up to you and your operations team.

   It is assumed that the <AppName>.XML file will be edited accordingly upon deployment to point to where the PB runtime folder was installed.

   You will need to co-ordinate this runtime / XML synchronization with your production rollout team.

Regards .. Chris

Your choices are:

All PB Runtime files in the same folder as the EXE

The PB Runtime folder gets added to the system path

The PB Runtime folder gets added to App Paths in the registry

The <appname>.xml file contains the correct path to the PB Runtime folder

Here is an example of the App Paths registry setting:

The app I work on uses the App Paths setting. Our installer software installs the PB Runtime into one folder and the application files in another. It sets the App Paths registry value as well.

After thinking about this more, I realized that I want to preset the install path in the runtime installer. Do I use the App Paths registry setting to set this or is there another way?

In the "Installing Powerbuilder Runtime" documentation, it says the following:

"PowerBuilder Runtime" is always installed to %systemdrive%\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime [version], for example, C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 22.0.0.1234"

When I generate the executables, in Run tab, the Runtime Path in Application XML is preset to 

C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 22.1.0.2828

When I run the runtime packager on my test computer, the runtime files are installed at:

C:\Program Files (x86)\Appeon\Common\PowerBuilder

But when I run it on a different computer it is installed at:

C:\Program Files (x86)\Appeon\Powerbuilder Runtime Packager

Why the inconsistency between computers? In powerbuilder 2019 the packager installed consistently at C:\Program Files (x86)\Appeon\Common\PowerBuilder. I am wondering why it is inconsistent with Powerbuilder 2022 R2.

We don't have a production rollout team that I can ask to help me with your suggestions. Any more help would be appreciated.

After reading the documentation a little more closely and considering the suggestion to put the runtime, I went ahead and added the runtime files to the MSI and it worked. For some reason I thought we had to run the runtime packager MSI in order for it to work.