Digital certificates are a core component of the Microsoft
Authenticode authentication and security system. Authenticode is
a standard part of the Windows operating system. To be compatible
with the .NET Framework security model, all PowerBuilder .NET applications
must be signed with a digital certificate, regardless of whether
they participate in Trusted Application Deployment. For more information
about Trusted Application Deployment, see the Microsoft Web site.

Signing manifests with digital certificates

You can select a digital certificate from a certificate store
or from a file browser. to sign your smart client application manifests.
You make the selection on the Sign page of the Project painter by
selecting the Sign the manifests check box in the Certificate group
box.

This table describes
the fields in the Intelligent Updater group box on the Sign page
of the Windows Forms Project painter. These fields are grayed out
when the Publish as Smart Client Application check box on the General
tab of the Project painter has not been selected.

Use the Select from Store or Select from File buttons to select
a certificate from a certificate store or from your file system.
If the certificate requires a password, a dialog box displays so
that you can enter it. When you select a valid certificate, detailed
information displays in the Project painter.

If you do not specify a certificate, PowerBuilder signs the
published manifest file with the default test certificate, mycert.fx.
This test certificate is installed by the PowerBuilder setup program
in the PowerBuilder DotNetpbiucommands directory.
However, when you are ready to publish a production application,
you should not sign it with the test certificate.

For information about application manifests required on the
Vista and later operating systems, see Security Requirements
.