New Script Packager Features: Execute Applications after Install

The features described in this article are included in PrimalScript 8.1.197 and PowerShell Studio 5.8.236.


The most common questions we get for the MSI builder are “How do I run my applications after the install?” and “How do I run a command x after install?”.

The answer to both of those questions is to use a custom action. But if you simply want to whip up an installer and show a readme after install, then creating a specific custom action may be beyond the scope of what you want to do.

User Interface

To simplify things, we added some fields to the User Interface settings which will make this easier for you.

image

Under Options, there are two settings to run an application after the installer has finished:

1. Execute application after install (no User Interface)

This does not require a user interface, and it runs before the installer exits. If your command contains spaces, it must be enclosed in quotes. This does not have to be an application included in the installer. The working folder is the installation directory.

2. Prompt for application start at exit (requires User Interface option)

This adds a checkbox option to the final dialog of the installer user interface to run the application, which will execute after or while the installer exits. The application must be a file installed with this installer, and it must also be an executable file. Use the ‘…’ button to select the desired file.

image

Both options can be used together in the same installer. Please note that the checkbox option does require your installer to have a user interface.

Related

Feedback

As always, if you have questions or comments, please post them here or in our support forum.