Custom install action c#

I am going to explore some of them since in the next step we will use these icons. Step 2: Clicking on 'file system editor' icon Adding project outputs to the installer: In simpler words, we are now adding files that we actually want to install and these files should be project outputs exe, dlls, etc. However there are more options available and one can add just a plain file, assembly, etc.

All these files along with dependencies referred files will be installed on the user system. Step 3: Define the target installation directory by setting 'Default location' That's It The project is ready as such and you can build it and distribute it. Now come some advanced topics and tunings. Advance Set up Options What if you want to check some condition and conditionally rollback the installation?

Step 4: Add custom Actions, click on the custom action icon Custom actions are for adding code that is needed to be executed during installation. Note: One important fact is that we can not run any code before installation starts, any code will run only after the installer dumps code files onto the user's system. To add a custom action click on the custom action icon.

This will open the following window and there we can add a project containing an installer class. To create this project having an installer class, we can make a class library type of project and add an installer class in it from the add new item dialog.

From the above two images, you can see a class library project, "my installer" and an installer class in it. To link this project to the installer project we add a "custom action" which is already shown before. Further, to send a parameter from the installer project to the custom action class we can use a custom action property, "custom action data".

You can receive this data in a class using a context object as follows: Context. Thanks for helping make community forums a great place. Click HERE to participate the survey. You may need to explain exactly what this means.

The same MSI file cannot be run twice to do an install, so there is no situation where the "product user again run the installer" does another install. Setups generated by VS and many other tools too show a dialog that includes choices to Repair or Remove the installed product, where Repair is just a check for missing files etc. So what exactly is this message that the installer displays? Is it this dialog or something else? After that user again run the Msi installer version 1.

Again run the Msi installer version 1. I will assume that "another MSI installer" means that you have created a RemovePreviousVersions upgrade and that this upgrade will be uninstalling the older product. The content you requested has been removed.

Ask a question. Quick access. Search related threads. Presumably, this could be fixed by adding an even lower sequence number to RemoveExistingProducts in the msi file, but I'm done fiddling with this for now. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow.

Learn more. Asked 5 years, 6 months ago. Active 1 year, 8 months ago. Viewed 11k times. This is the code of the Install Class: using System. Collections; using System. Commit savedState ; SettingsControl. Parameters["assemblypath"]; SettingsControl. Thodor12 Thodor12 2 2 gold badges 2 2 silver badges 12 12 bronze badges.

Add a comment. Active Oldest Votes. On the View menu, point to Editor, and then click Custom Actions. The Custom Actions Editor is displayed. In the Custom Actions Editor, select the Commit node. On the Action menu, click Add Custom Action. Select Primary output from InstallerActions project. In the Properties window, make sure that the InstallerClass property is set to True this is the default.

Yoruba Yoruba 2, 19 19 silver badges 23 23 bronze badges. You should provide more details in your answer, as external links can break over time. So if I get it right, after the commit, find the settings file and edit it directly? I stumbled upon this: stackoverflow. Is this also true for VS? If that is the case then I know why my code isn't working. That doesn't seem relevant based on your problem because it refers to debugging and a missing base.