Using Custom Actions

InstallShield 2015

Project: This information applies to the following project types:

•

Basic MSI

•

DIM

•

InstallScript MSI

•

Merge Module

•

MSI Database

•

MSM Database

•

Transform

InstallShield supports the use of custom actions to run InstallScript, VBScript, or JavaScript code; call DLL functions; run executable files; call a managed method in a managed assembly; set a property or a directory; trigger an error and end the installation; run PowerShell scripts; terminate a process; or run other installation packages.

InstallShield divides the task of creating and implementing custom actions into the following steps:

Create a custom action in the Custom Actions and Sequences view (or the Custom Actions view) or by using the Custom Action Wizard.

Decide when your custom action should run.

Launch a custom action by inserting it into a sequence or placing it as the result of a dialog’s control event (Basic MSI projects).

For details about each of the InstallShield custom actions that are added automatically to InstallShield projects to support different functionality, see InstallShield Custom Action Reference.

Project: Merge module projects only: You can control the launch of custom actions in a merge module by modifying the ModuleInstallExecuteSequence table in the Direct Editor. When you add the merge module to your installation project, all custom actions and dialogs included in the merge module are available for you to insert in the installation’s sequences via the Custom Actions and Sequences view.

Using Custom Actions

InstallShield 2015 Help Library

June 2015