This custom action is written in VBScript. See also Scripts.

Source

The Source field of the CustomAction table contains the null value. The script code for the custom action is stored as a string of literal script text in the Target field.

Type Value

Include the following value in the Type column of the CustomAction table to specify the basic numeric type of a 32-bit custom action.

Constants	Hexadecimal	Decimal
msidbCustomActionTypeVBScript + msidbCustomActionTypeDirectory	0x026	38

 

Windows Installer may use 64-bit custom actions on 64-bit operating systems. A 64-bit custom action based on scripts must include the msidbCustomActionType64BitScript bit in its numeric type. For information see 64-bit Custom Actions. Include the following value in the Type column of the CustomAction table to specify the basic numeric type of a 64-bit custom action.

Constants	Hexadecimal	Decimal
msidbCustomActionTypeVBScript + msidbCustomActionTypeDirectory + msidbCustomActionType64BitScript	0x0001026	4134

 

Target

The Target field of the CustomAction table contains the script code for the custom action as a string of literal script text.

Return Processing Options

Include optional flag bits in the Type column of the CustomAction table to specify return processing options. For a description of the options and the values, see Custom Action Return Processing Options.

Execution Scheduling Options

Include optional flag bits in the Type column of the CustomAction table to specify execution scheduling options. These options control the multiple execution of custom actions. For a description of the options, see Custom Action Execution Scheduling Options.

In-Script Execution Options

Include optional flag bits in the Type column of the CustomAction table to specify an in-script execution option. These options copy the action code into the execution, rollback, or commit script. For a description of the options, see Custom Action In-Script Execution Options.

Return Values

This custom action type always returns success.

Remarks

A custom action that is written in JScript or VBScript requires the install Session object. The installer attaches the Session Object to the script with the name "Session". Because the Session object may not exist during an installation rollback, a deferred custom action written in script must use one of the methods or properties of the Session object described in the section Obtaining Context Information for Deferred Execution Custom Actions to retrieve its context.

See Also

Custom_Actions

Send comments about this topic to Microsoft

Build date: 8/13/2009