Use this dialog box to specify the default values used for signing cabinet files and setup files (distribution units). You can specify the certificate to use by default when signing cabinet and setup files. These values can be overwritten in the individual settings dialog boxes for the cabinet and setup files.
These signing options are also used when you deploy server-side components (COM components and Java classes that run on the Web server/deployment target). The development environment uses the signature file specified here when the deployment target requires that all components be signed before they can be installed on the deployment target.
Provides a place to enter or edit the location of the certificate file (.spc) you want to use to sign this distribution unit. To locate an existing certificate file, click Browse. To get a certificate file, contact a certificate file provider.
Provides a place to enter or edit the location of the private key file (.pvk) associated with this certificate.
Specifies that the distribution unit should be signed. If you sign a distribution unit, you identify yourself to the user before they download the software. Signing also verifies that the file has not been tampered with since you signed it.
Provides a place to enter or edit the location of a timestamp server. A timestamp server validates the date and time that the distribution unit was signed. Certificate files can expire after a certain period of time. Contact your certificate file provider (certificate authority) for the location of their timestamp server.
Resets the distribution unit signing options to the development environment's default values set in the Tools menu, Options dialog box, Security node.
Signs the distribution unit with the Microsoft® Visual Studio™ test certificate. The Visual Studio test certificate is provided to support test scenarios only, and should not be used for signing distribution unit files that you deploy to an intranet or the Internet. The text for the Visual Studio test certificate indicates that the user should not trust the signed component based on the test signature.
Enables the use of a personal or corporate signature file (certificate) to sign the distribution unit.