Visual studio windows application setup project 2010

Once this is done, locate your project in Visual Studio, go into the Debug folder and you will see two different installers used for two different purposes:. Test the installer by double-clicking one of them eg setup. Look on the desktop and program menus to check that all of your program shortcuts, files, folders etc have been correctly installed.

Hi Andy, Thank you for the detailed description. Please enlighten me! Yes, it was the exectuable contained in the Debug or Release folder that I had in mind, that exe which when you double-click on it runs the application you are working on. I will update this post to clarify this point better…. Andy, thanks a lot for great instructions. Couple of questions: where you live off you still have to have 2 files to run the install: — setup. Also, is the only way to set up verbose logging is to run the msi directly through cmd line?

I have not used the installer feature in any depth. The msi file by itself should be sufficient. Got article. I wonder, do you know how to make this installation to be dynamic and capture the folder path? So in case user choose another folder to install an application this information can be captured and then tell the code where to find resource file.

This regarding an app which will write to external file such as. In my case, app needs to write log files and other files that must be strored in appdata folder Win7 later not allow to change files in app folder. Could you please add that portion? Hi Daniel. Thanks for the feedback. Any further insights you might have in the meantime would be much appreciated. Hi Sub Dee, I have never used installer in that way. If you get any further insights I would be happy to know. Can the Visual Studio installer be used to create a 2 way installation using a radio button?

What I mean is, can you create an installer that asks you to choose which version of the program you want to install admin side or client side? If this is still not clear, I can send a screenprint of an example.

I made installer according to above instructions but when I run the application by clicking application shortcut icon, following error occured. The server was not found or was not accessible. Verify that instance name is correct and the SQL server is configured to allow remote connection.

When I create the installer the class wizard no longer works. Everything is working except the class wizard. NET framework 3. After that you can see one pop up there you can select the prerequisites button then select what all prerequisites needed for your application to run Select any of the 3 radio buttons select 1st one Default.

Now you can design your setup. You can give a banner image b. You can change the Copyright Warning message, welcome text, etc. After build success, you can see in your project folder one extra folder created. Inside the Debug folder, you can see your setup file as shown below. Step 2: Rebuild your application. This folder contains some files. Follow this step for open setup wizard. Step 5: Click on next button for next steps.

Step 6: Click next button for next steps. Step 8: Click on next button for next steps. Step 9: Now setup are created.

We find an msi and a setup. You can run either to initiate setup. When we started we saw a setup wizard with screens that welcomed the user, asked for the location to install while the default location was already set. Now if we navigate out to the installation location we can also see the Input folder created and the Sample. Custom actions are the actions which contain customized functionality apart from default one at the time of installation and uninstallation.

For example, my QC team reported a bug that when running the application while simultaneously in background uninstalling the application, the application still keep on running. As per them it should show a message or close during the uninstallation. It was hard to explain to them the reason for this, so I opted for implementing their desire in the setup project. The code contains the logic to find the running EXE name at the time of uninstallation.

If it matches my application EXE name, it kills the process. Not going into more details to it. Just want to explain the use of custom actions. What if the installation machine does not have a. NET framework? We can specify our own package supplied with installation so that our application does not depend on the. NET framework of the client machine, but points to the package we supplied to it to run.

Here we can specify pre-requisites for the application to install. Just click on Prerequisites button and in the opened prerequisites window, select the checkbox for the. NET Framework application that needs to follow, and select the radio button at number 2 i.

Download prerequisites from the same location as my application.