![]() ![]()
See the Property Definition Placeholders section of this document for the list of available placeholders. The Command Line field supports the property definition placeholders, so you can use the standard MSI properties while configuring the action. If you need to run an executable that isn’t available on each system where the package will be deployed, use any of the options above. The custom action will work only if the configured executable with the same file path is available on the system where the package will be deployed. INSTALLSHIELD CUSTOM ACTION COMMAND LINE PARAMETERS WINDOWSThis option allows you to select a location on the local file system and is applicable only to run standard Windows commands. They replace absolute paths to the files location with placeholders to represent special system folders to make the package independent from the deployment environment. When you select a file from those available in the project, the path to the file may be represented using the property definition placeholders. INSTALLSHIELD CUSTOM ACTION COMMAND LINE PARAMETERS INSTALLUse it when you need to run a file that is a part of the deployed installation after install or before uninstall. You cannot use it to run a command after uninstallation, because the file is already deleted. ![]() You cannot use it to run a command before installation, because the file to be executed isn’t deployed yet. This file is a part of deployed changes, so you can run it. This option can be used, for example, to run a file that is a part of the captured installation, for example. The executable/script file should be available in the File System section of the project. This option allows you to run an executable or a script deployed by the package. Other options, represented below, have limitations and aren’t as flexible as this option. Custom actions operate with the own set of files always available in all the cases, so, for example, you can execute a custom script before package installation or after uninstallation, for example. 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |