HomePowerBuilderAppeon Documentation Center

Signing native C/S app in project painter

Code signing for native client/server application executable files is integrated into the project painter now, allowing automatic signing during the build process (previously signing native C/S application can only be done manually via custom scripts).

The Signing options are added to the Security tab of the native client/server Application project painter. You can sign the native client/server app in exactly the same way as signing PowerClient and PowerServer apps. For more details, refer to the section called “Digitally signing the executable application” in Application Techniques.

The signing options are also supported in PBAutoBuild and ORCA.

  • PBAutoBuild

    "Security": {
   "Signing": {
      "SignOptions": 1,
      "//SignOptions": "0: Do not sign the executable file; 1: Use the SignTool utility from the Windows SDK; 2: Use your own signing script (*.cmd);",
      "UseTheSignTool": {
         "SignToolLocation": "D:\test\signcode.exe",
         "CertificateType": 0,
         "CertificateThumbprint": "",
         "CertificatePath": "D:\test\mycert.pfx",
         "CertificatePassword": "MA==",
         "SignatureAlgorithm": "SHA512",
         "URLOfTheTimestampServer": "http://timestamp.digicert.com"
      },
      "UseYourOwnSigningScript": ""
   },
}

  • ORCA

    set exeinfo property <signingoptions> <0 | 1 | 2>
set exeinfo property <signtype> <0 | 1 >
set exeinfo property <signtoollocation| signthumbprint| signpath| signpassword| signalgorithm| signtimestamp| signscript> propertyString
Prev  Up  Next
Enhanced DLL loading security  Home  Advanced executable security flags (beta feature)