advanced installer custom action action data

Using a File from Actions Files allows you to run executables/scripts independently from the type of the custom action (before/after install/uninstall) and environment.

You can add command-line parameters to the command, if required. When you select a file, it is represented as $$ is a property definition placeholder that specified a path to the storage of custom action files. If you have been added custom actions files, you can use the Select a File from the Actions Files button of the Command Line edit box to configure a file to be executed as a custom action. To specify a command using an executable/script file use buttons available in the Command Line edit box. Or you can configure action files, as explained below, and use them to run an action. Custom actions executed before install or after uninstall can run scripts/executables always available in a system, for example system commands. A custom action can run executable and script files that is a part of deployed package, but for actions executed before install or after uninstall these files are not available because the installation isn’t deployed them (in the case of before install action) or already deleted them (in the case of after uninstall action). It’s important to understand when the action will be executed to configure a command properly. The action to be executed should be specified in the Command Line field, where you can also configure optional command-line parameters to be passed to the executable/script.Ī custom action can be executed before install of the package, after install, before uninstall or after uninstall. Each pre & post action can be represented with a command (such as an executable or script file) or a simple action to open a file or an URL.

Advanced installer custom action action data