Related features

The following changes have been made in accordance to the decoupling of runtime and IDE.

  • A new property RuntimePath is added to the Environment object to get the runtime path and version used by the current application executable.

  • A system function GetInstalledRuntimes is added to get the version number of runtimes that are installed on the current computer.

  • A system option "Show prompt for full-building a target if it is opened after PowerBuilder Runtime change" is added -- Every time after you changed the version of PowerBuilder Runtime for the current IDE and restarted IDE, you will be prompted to full build the application. In most cases, it is recommended to full build your application every time after the runtime version is changed, unless your application is large and takes a long time to full build, then you can clear this check-box and manually full build the application only when there is a major version change for PowerBuilder Runtime. And once you performed a full build in the IDE, the new runtime version will be recorded in "appruntimeversion" which is an internal property used by the IDE only. (Note creating an exe from PBC, OrcaScript or IDE will not update the version number in the "appruntimeversion" property.)

  • When using OrcaScript commands, you can use the runtime_version argument to specify the version of PowerBuilder Runtime that will be used to compile the application executable, for example, OrcaScr190 /D runtime_version="" C:\test\test.bat. For more, refer to the section called “OrcaScript Commands” in Users Guide.

  • When using PowerBuilder Compiler (PBC), you can use the /rt argument (for example, /rt to specify the version of PowerBuilder Runtime that will be used to compile the application executable. And PowerBuilder Compiler must be installed after PowerBuilder Runtime is installed. For more, refer to the section called “Appendix B. PowerBuilder Compiler” in Users Guide.

  • The MSI/MSM file generated by the PowerBuilder Runtime Packager 2019 R3 tool has been enhanced, so that runtime files of different builds at the same major version (starting from 2019 R3 GA) can be installed and coexisting on the same computer, for example, 2019 R3 and 2019 R2 can coexist, multiple 2019 R3 MRs can coexist. And the MSI file no longer sets the runtime file path in the system PATH environment variable; therefore, the user will need to decide which build of runtime files will be loaded by the application executable file and place the application executable and the runtime files in the same folder.