|
|
||
MSI Factory
Creates a custom action that runs a JScript file. Corresponds to Windows Installer custom action types 21, 37 and 53.
See the Attributes tab for more details about scheduling, run options and return values.
If selected, the JScript file (.js) will be stored in and called from the Binary table of your Windows Installer database.
The full path and filename of the JScript file on your local development system. You can click the Browse button to select a file.
If selected, the JScript file is a file that you are installing with your software. 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 script.
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 script file in your project. You can click the Browse button to select an identifier.
If selected, the literal JScript text will be specified. You should only use this option for very short, single line scripts.
The literal script text to run.
The name of the JScript function to call. Only valid if Location is "Internal binary" or "Installed with product."
If checked, the script targets a 64-bit platform.
MSDN Online: 64-Bit Custom Actions
MSDN Online: CustomAction Table
MSDN Online: Custom Action Type 21
MSDN Online: Custom Action Type 37
MSDN Online: Custom Action Type 53
MSDN Online: Scripting
MSDN Online: Scripts
MSDN Online: Summary List of All Custom Action Types
WiX Help File: CustomAction Element
Learn More: Indigo Rose Software - MSI Factory - Buy Now - Contact Us