Setup Factory for Windows Installer
Creates a custom action that runs an executable file. Corresponds to Windows Installer custom action types 2, 18 and 50.
See the Attributes tab for more details about scheduling, run options and return values.
If selected, the executable file will be stored in and called from the Binary table of your Windows Installer database.
The full path and filename of the executable on your local development system. You can click the Browse button to select a file. You can use a relative path in this field. The path will be relative to the location where the project (.sufproj) file is saved.
If selected, the executable is a file that you are installing with your software. This type is commonly used if you want to run your software after installation. In this case, the timing of the action (see the Attributes tab) must adhere to the following rules:
1. The custom action must be sequenced after the CostFinalize action. This is so that the custom action can resolve the path needed to locate the executable.
2. If the source file is not already installed on the computer, deferred (in-script) custom actions of this type must be sequenced after the InstallFiles action.
3. If the source file is not already installed on the computer, non-deferred custom actions of this type must be sequenced after the InstallFinalize action.
The identifier of the executable file in your project. You can click the Browse button to select an identifier.
If selected, the full path and filename of the executable will be specified with the value of a property. This is commonly done when you are finding the executable during installation using a search.
The name that uniquely identifies the property. You can click the Browse button to select a property.
If selected, you can specify the full path and filename of the executable file as well as a working folder (directory) for the execution. This option can be useful if you want to specify an absolute path to an executable, or if you need to set a different working folder for the action.
The fully-qualified path to the file to run. If the path does or may include long filenames, you must include quotes around it. You can use properties and folder references to help resolve the path. For example, "[WindowsFolder]notepad.exe."
The working folder to be set when running the executable. It must be a folder reference to a folder in your project. For example, "INSTALLDIR." You can click the Browse button to select a folder from the Folders dialog.
Command line arguments that you want to pass to the executable when it is run. Make sure to include quotes around arguments that could contain spaces. For example: -q "-log:My log file.txt."
MSDN Online: CustomAction Table
MSDN Online: Custom Action Type 2
MSDN Online: Custom Action Type 18
MSDN Online: Custom Action Type 34
MSDN Online: Custom Action Type 50
MSDN Online: Executable Files
MSDN Online: Summary List of All Custom Action Types
WiX Help File: CustomAction Element