What's New
Decoupling Runtime and IDE

The runtime files (including .dll, .ini, .pbx, .pbd etc.) are renamed so that the version number indicator (such as "170", "190") that used to be appended to the file name is removed, for example, pbvm190.dll is renamed as pbvm.dll, pbdom190.pbd is renamed as pbdom.pbd.

If your application uses pbwsclient.pbd, pbdom.pbd, pbsoapclient.pbd, pbejbclient.pbd, make sure to update the file name and path accordingly.

All runtime DLLs that used to be installed to the "Shared" folder are now separately installed to the "Runtime [version]" folder and the "IDE" folder instead, in order to physically separate Runtime files from IDE files.

The "Runtime [version]" folder contains the libraries required at runtime. Example location: C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 19.2.0.2556.

The "IDE" folder contains the support files required by IDE. Example location: C:\Program Files (x86)\Appeon\PowerBuilder 19.0\IDE.

If any external program has called the runtime file, you may need to change the code accordingly in order for the program to find the dependent DLLs successfully (view a code example here).

The runtime file location is no longer recorded in the system PATH environment variable; it is recorded in the system registry instead.

The 32-bit apps in 32-bit OS search for this registry: HKEY_LOCAL_MACHINE\SOFTWARE\Sybase\PowerBuilder Runtime

The 32-bit apps in 64-bit OS search for this registry: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sybase\PowerBuilder Runtime

The 64-bit apps in 64-bit OS search for this registry: HKEY_LOCAL_MACHINE\SOFTWARE\Sybase\PowerBuilder Runtime

The PowerBuilder IDE (and the application executable) can select which version of runtime files will be used, so it enables developers to easily maintain multiple projects. The IDE can compile for multiple runtime versions (both minor and major) through the System Options. See the section called “Selecting a version of PowerBuilder Runtime” in Application Techniques for detailed instructions.