advanced installer custom action inline script recursive

Each custom action must have a unique name. On the installer setting dialog, we have a new page “Custom Actions.” As you may have guessed, here is where you define them. In addition to the application, we add two PowerShell scripts (setvalue.ps1 and removevalue.ps1) and a readme.txt: We will use a simple WMI Explorer generated application to illustrate these custom actions. All the powerful functionality of Windows PowerShell is now at your disposal during installer operations. Likewise, you can create registry entries and remove them again as needed. You can create actions which will then remove these modules again during uninstall. With custom actions you can install modules you need from the PowerShell Gallery or any other repository. This is where custom actions come into play. While Windows Installer has some functionality for creating registry entries-chaining other Windows installers (e.g., for dependencies), or opening ports in your firewall-it has very little functionality to support PowerShell or its modules. Any files or documents created by the user or created during normal operation of a product are not removed. Likewise, when uninstalling, it uses information created while installing to remove files that have been previously copied to your hard drive. When installing or updating a product, Windows Installer’s main job is to copy the files of a product to the proper place. If you are not familiar with custom actions for Windows installers, here is a brief overview:

Overview: Custom Actions for Windows Installers Most commonly you will probably use executable files or a PowerShell Script. A custom action is anything that can be executed from a command line. Starting with PrimalScript 2018, version 7.4.111 you can define custom actions for your Windows Installers.

Advanced installer custom action inline script recursive