While the build process will warn you if there is a name collision, here is a list of names you should not use: CreateFoldersĬonfiguring your Custom Actions Properties If you choose the name of an internal action (e.g., ‘RegisterProduct’), the internal action will be executed instead of your custom action. Because Windows Installer has many internal actions, you must be mindful of their names. The first decision is what to name your custom action, which you will add to the list on the left. So if you want to run a particular PowerShell script during install, that script file must be part of your installation. For example, if you want to associate a file type with your product or copy a registry key from an old version to the new version, custom actions are what you need.Ī custom action can be any executable, script, or anything that exists on the target machine during install time. Most installers will require admin privileges, whereas most applications do not and should not run elevated. The sixth part of our step-by-step series for the MSI builder explains custom actions.Ĭustom actions enable you to do additional setup, removal, or repair-which you may not be able to do from your application.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |