Connection Information

To perform the requested action, WordPress needs to access your web server. Please enter your FTP credentials to proceed. If you do not remember your credentials, you should contact your web host.

Connection Type

What changes made for the decoupling – PB Docs 2021 – PowerBuilder Library

What changes made for the decoupling – PB Docs 2021

What changes made for the decoupling

The following changes have been made to decouple 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/pbwsclient.pbx,
    pbdom.pbd/pbdom.pbx, pbsoapclient.pbd/pbsoapclient.pbx, or
    pbejbclient.pbd/pbejbclient.pbx, 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)AppeonCommonPowerBuilderRuntime 19.2.0.2556.

    The “IDE” folder contains the support files required by
    IDE. Example location: C:Program Files
    (x86)AppeonPowerBuilder 19.0IDE.

    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 code
    examples
    ).

  • 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_MACHINESOFTWARESybasePowerBuilder Runtime

    The 32-bit apps in 64-bit OS search for this registry:
    HKEY_LOCAL_MACHINESOFTWAREWow6432NodeSybasePowerBuilder
    Runtime

    The 64-bit apps in 64-bit OS search for this registry:
    HKEY_LOCAL_MACHINESOFTWARESybasePowerBuilder Runtime

  • A configuration file is automatically created by default
    using the same name under the same directory as the application
    executable. For example, if the application executable is
    app1.exe, then the configuration file is app1.xml.

    You can specify the version of PowerBuilder Runtime in the
    configuration file. See the section called “Selecting a version of PowerBuilder Runtime” in Application Techniques for detailed
    instructions.

  • 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.


Document get from Powerbuilder help
Thank you for watching.
Was this article helpful?
Subscribe
Notify of
guest
0 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x