MSI Factory

Build

Build Defaults

Open output folder after build

Make MSI Factory open the output folder by default after a build has completed. This setting is also available on the Build Progress dialog.

Confirm before building

If selected, MSI Factory will confirm the build process before continuing. If unselected, the build will start immediately. This setting does not affect unattended builds.

Save log file

Make MSI Factory save a text log file in the output folder containing all of the build information. This setting is also available on the Build Progress dialog.

Default output folder:

The full path to the folder where MSI Factory will store the file(s) generated during the build process. You can click the Browse button to select a folder. This setting can be found on the Setup File tab of the Build Settings dialog.

Default working folder:

The full path to the folder where MSI Factory will store any temporary build files that it needs to generate during the build process. You can click the Browse button to select a folder.

Code Signing Defaults

These settings are the default values that will be used on the Code Signing tab of the Build Settings dialog when new projects are started.

Code sign setups

Code sign all new setups during the build process. If you are building a bootstrapper, the bootstrap executable will also be signed with these settings. See Authenticode Code Signing for more information.

Code signing tool:

The tool you want to use to digitally sign all new project setups. Choose from:

SignTool.exe

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).

SignCode.exe

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).

Tool location:

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.

Certificate filename:

The full path and filename of the certificate to use for signing all new project setups. 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).

Private key filename:

The full path and filename of the "Private Key" file (*.pvk) to use for signing all new project setups. This file is only used when SignCode.exe is the selected tool. You can click the Browse button to select the file.

Timestamp URL:

The URL of a timestamp DLL on the Web to use for all new setups, such as: http://timestamp.verisign.com/scripts/timstamp.dll. If you do not want to timestamp the setup file, leave this field blank.

Other arguments:

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. MSI Factory automatically passes the "sign" argument when "SignTool.exe" is the selected tool.