Windows Installer Editor Reference
490
Custom Action Reference
z
Sequence
Select a sequence to which to add this custom action. The options here correspond
to the sequences available with each of the three installation modes of a standard
installation (.WSI or .MSI file).
z
Reference Action
This drop-down list contains all the standard Windows Installer actions from the
sequence that you selected in the Sequence drop-down list. This custom action,
when merged into a standard installation, will be placed relative to the action you
select in this list.
z
Sequence Number
If the reference action you select above is not found, this custom action will be
placed using this sequence number. In most cases, you can ignore this field. You can
view sequence numbers for a particular sequence by viewing the sequence in the
Tables tab in Setup Editor.
In the Placement section, mark an option to specify where to place this action:
Before Action
Click this option to place this action before the Reference Action you selected
above.
After Action
Click this option to place this action after the Reference Action you selected
above.
z
Condition
If you want this action to run only if a certain condition is true, enter a condition. In
the User Interface, Execute Immediate, and Execute Deferred sequences, the
condition you enter is displayed as an If Statement preceding the custom action. To
use the Condition Builder to create a syntactically correct Windows Installer
condition, click Build.
See
Creating Conditions With Condition Builder
on page 391.
See also:
All Custom Actions
on page 442
Using the Custom Action Properties Tab
The Properties tab appears on the details dialog box for most custom actions. However,
sometimes options are unavailable or display different choices based on what kind of
custom action you added and where you added it. In this dialog box, you set options
that determine when and how the custom action is run.
In-Script Options
This determines when the custom action is executed. When Windows Installer runs the
installation, it first reads the action sequences and creates its own internal installation
script to follow, then later it executes that script. You can have the custom action
executed immediately when Windows Installer first encounters it, or later during
execution of the internal script.
See Custom Action In-Script Execution Options in the Windows Installer SDK Help.
