Setup and deployment custom actions

Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually.

Now application settings dialog will come as shown below. Here we have to select " DLL " and click " Finish " button. Now here we can create the custom action functions which will be called by the installer. For this article, I have created 3 custom actions functions. For the first two functions, company name will be passed as a parameter. The code snippet for getting parameter is:. In the above code snippets, " MsiGetProperty " is called with an empty buffer string for getting size of parameter passed.

Buffer size is increased for accommodating null character and then MsiGetProperty is again called for getting the parameter passed to the custom action. After getting parameter, application specific task can be done. In my demo installer, I have created a registry key with the parameter passed to the custom action function. For successful compilation of the custom action DLL " Msiquery.

More details about the custom action code is present in the attached source file. After successful compilation of custom action DLL, it needs to be added to the installer project. This custom action DLL should be added to the installer project in the same way as application files are added to the project in figure 2.

We have completed the task of creating and adding custom action DLL into the installer project. Now I am going to show steps for adding this custom action function in our installer project. A custom action view is shown which contain " Install ", " Commit ", " Rollback " and " Uninstall " filters. Custom action function under " Install " filter is called when installer is copying the application files in destination machine.

Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy. IT Professionals can customize a feature update by running their own custom action scripts during and after a feature update.

Custom actions are available starting with Windows 10, version Custom actions are. These can be run during four phases of a feature update:. Placing a shortcut somewhere? When I say custom actions, creating a class using the. As long as your new console app is updated in your install project, and you are releasing the new version of the installation, it should work just fine — S.

So if I install the project using the MSI, into the program files directory, and copy the console. Krishna I did some testing and you are indeed correct - feel free to add your comment as an answer and Ill mark it as such : — m.

Add a comment. Active Oldest Votes. Improve this answer. Krishna S. Krishna 11 11 silver badges 26 26 bronze badges. Just a note of discovery as well, if the custom actions are removed from the console application, and an uninstallation is started - it will fail. The custom actions need to remain in the console application for the uninstallation to work.

Cheers S.