)OverviewSetup FileConstantsCode SigningResourcesPre/Post Build
Tip: See the Code Signing Defaults section of the build preferences (Edit > Preferences, Code Signing) to configure default values when creating new projects.
Tip: If you want full control over the how the setup is code signed, you can leave all fields blank except for Tool location, and specify all options in the Other arguments field. When "SignTool.exe" is the selected tool, Setup Factory automatically passes the option "sign".
The build configuration you want to use when generating your final setup. The drop down contains all of the current build configurations. A build configuration contains all previously saved information on the Setup File, Constants, Code Signing, Resources, and Pre/Post Build tabs.
)Opens the New Build Configuration dialog where you can create a new build configuration in your project.
)Removes the current build configuration from your project.
Note: There must be at least one build configuration in your project.
)Renames the current build configuration.
If checked, the setup and uninstall will be code signed during the build process using the settings below. See Authenticode Code Signing for more information.
The tool you want to use to digitally sign the setup. Choose from:
Use SignTool.exe to digitally sign the setup file. This tool could not be distributed, but is available in the \Bin folder of the Platform Software Development Kit (SDK). This tool is not supported on Windows NT/Me/98/95. For more information, see MSDN: SignTool (Windows).
Use SignCode.exe to digitally sign the setup file. 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 when signing the setup file. 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.
Tip: If your .PFX file is password protected, you must pass its value in the Other arguments field using the /p option. For example: /p "mypassword". For more information, see MSDN: SignTool (Windows).
The full path and filename of the "Private Key" file (*.pvk) to use for signing. 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 such as: http://timestamp.verisign.com/scripts/timstamp.dll. If you do not want to timestamp the setup file, leave this field blank.
The description of the signed content.
A URL that provides further information about the signed content.
Any additional options you would like to pass to the code signing tool. If you leave any of the above fields blank (except for tool location), you can pass their values as command line options. Setup Factory automatically passes the "sign" argument when "SignTool.exe" is the selected tool.