Summary

Synopsis

Discussion

To add a custom action to a Merge Module project, two major tasks are necessary: Creating the custom action, and inserting the custom action into the sequence. Follow the steps below to accomplish these main tasks:

1. Select the Custom Actions view within the Merge Module project.
2. Right-click on the top of the Custom Actions tree in the center panel, and choose Custom Action Wizard...
3. Follow the prompts in the Wizard to create your desired custom action*.

1. Select the Direct Editor view within the InstallShield IDE.
2. Review the Custom Action table, and note the name of your custom action in the Action column. It should now have a GUID appended to it (example: MyCustomAction.D941D8C1_325E_4006_9527_945EDA97F5B1).
3. Select the ModuleInstallExecuteSequence table.
4. Create a new row in this table. In the Action column, enter the name of your custom action with the GUID appended as listed in Step 2 above.
5. In the BaseAction column, enter the standard action or custom action you'd like your new custom action to launch after.
6. In the After column, enter a value of "1" to notify the installer to run your new custom action after the action listed in the BaseAction column. A value of "0" can also be entered if you wish to launch it before the action specified.
7. In the Condition column, enter a condition of your choice or leave null for it to run every time.
8. The action you entered in the BaseAction column (Step 5 above) must also have it's own row in this table. If it does not have a corresponding row, then one must be created*.

*Note: When creating a corresponding row for the action entered in the BaseAction column, if the value specified in the BaseAction column is a standard action, the sequence number can be found by opening a Basic MSI project and looking in the Sequences view. In the example below, CostFinalize has a sequence number of "1000", so this value is entered into the table as specified.

Additional Information

This information can also be found in the following Microsoft MSDN articles:

• ModuleInstallExecuteSequence Table
• Authoring Merge Module Sequence Tables
• Merge Module Database Tables