OverviewCode Signing
These settings are the default values that will be used on the Code Signing tab of the Project Settings dialog when new projects are started.
Code sign all new AutoPlay applications during the build process.
The tool you want to use to digitally sign all new AutoPlay projects. Choose from:
Use SignTool.exe to digitally sign the application executable. This tool could not be distributed, but is available in the \Bin folder of the Platform Software Development Kit (SDK). For more information, see MSDN: SignTool (Windows).
Use SignCode.exe to digitally sign the application executable. This tool could not be distributed, and only ships with the .NET Framework SDK version 1.0 and 1.1. For more information, see MSDN: File Signing Tool (Signcode.exe).
The full path and filename of the chosen code signing tool on your system (SignTool.exe or SignCode.exe). You can click the Browse button to select the file.
The full path and filename of the certificate to use for signing all new AutoPlay applications. If SignTool.exe is selected, this file must be a "Personal Information Exchange" file (*.PFX). If SignCode.exe is selected, this file must be a "Software Publisher Certificate" file (*.SPC). You can click the Browse button to select the file.
The full path and filename of the "Private Key" file (*.pvk) to use for signing all new AutoPlay applications. This file is only used when SignCode.exe is the selected tool. You can click the Browse button to select the file.
The URL of a timestamp DLL on the Web to use for all new AutoPlay applications, such as: http://timestamp.verisign.com/scripts/timstamp.dll. If you do not want to timestamp the application, leave this field blank.
Any additional options you would like to pass to the code signing tool. If you leave any of the code signing fields blank (except for tool location), you can pass their values as command line options. AutoPlay Media Studio automatically passes the "sign" argument when "SignTool.exe" is the selected tool.