Running external programs during installation

You can run external programs as custom actions during installation. See Installing Third-Party Software and the Advanced - Actions project page help file for more information about adding custom actions to your project.

How do I run a batch file or script during installation?

By creating a custom action that runs the batch file or script. See Installing Third-Party Software and the Advanced - Actions project page help file for more information about adding custom actions to your project.

There are two ways to run a batch file or script as part of a custom action:

• Using ShellExecute() - Specify the name of the batch file or script as the Target path of the action in its Action settings pane, and check its Open with ShellExecute() box. This assumes that the customer's system is properly setup and that the Windows Shell executes batch files or scripts on Open. This is Windows' default behavior, but it can be changed by the customer. Also, only recent versions of Windows support scripts.
• Using a command processor - [Applies to batch files only] Specify <ComSpec> as the Target path of the action and /c followed by a space and the name of the batch file as its Arguments; make sure that the Open with ShellExecute() box is cleared. The <ComSpec> variable resolves to the fully qualified path of the command processor (usually Command.com for Windows 9x and Cmd.exe for Windows NT); the /c option ensures that the command prompt window will close when the batch file has run to completion.

Note that in both cases you should specify the fully qualified path to the batch file as its name, if necessary by using project variables for the installation- or system dependent parts.

How do I open a command prompt window during installation?

By creating a custom action that runs the command processor. See Installing Third-Party Software and the Advanced - Actions project page help file for more information about adding custom actions to your project.

In the newly created custom action, specify <ComSpec> as the Target path of the action. The <ComSpec> variable resolves to the fully qualified path of the command processor (usually Command.com for Windows 9x and Cmd.exe for Windows NT); make sure that the Open with ShellExecute() box is cleared.

Depending on your other needs, you should set the other action options as appropriate. See the previous topic for information about running a batch file in a command prompt window.

How do I display a prompt before running an external program?

By checking the Prompt option in the action's Action settings pane and entering the desired prompt text. This will cause Setup to display a message box with the text that you specified and Yes and No buttons. The external action will only be run if the customer clicks Yes.