In this tutorial I will show how to deploy a C# application using a standard Visual Studio Setup Project.

Any application must be somehow provided to the end-user. If the application is very small and is composed of a single executable, it can be deployed by just providing the executable to the end user. In our situation, the application has many dependencies, that can or cannot be present on the client machine, so we need to create a setup project, that will install the needed dependencies and the application itself.

Special Tutorial Requirements:

• Microsoft Visual Studio 2008 ('Setup and Deployment' projects are not available in Express editions)

Let's start.

1. First of all we need to open a C# project/solution (or any other project/solution you have made using one of the programming languages included in Visual Studio). Use 'File -> Open -> Project/Solution' (or Ctrl+Shift+O):





2. After opening a C# project/solution you will get something like this:



3. Now you have to add a setup project to the current solution. Use 'File -> Add -> New Project...':



4. In the 'Project types' list, go to 'Other Projects -> Setup and Deployment' and select the 'Setup Wizard' template:



As you see there are many 'Setup and Deployment' project types and you can create just a blank setup project and customize it by yourself, but in this tutorial I will show how to use the wizard, which is a little bit easier for beginners.

5. Now let's take a deeper look at the wizard.

The wizard is composed of 5 general steps:

Step #1: Initialization



This step is a 'welcome message'.

Step #2: Project Type



In this window you have to select the setup project type. You have four options:

To create a setup program to install an application:

1. Create a setup for a Windows application
2. Create a setup for a web application

To create a redistributable package:

1. Create a merge module for Windows Installer
2. Create a downloadable CAB file

I will use the 'Create a setup for a Windows application', as my C# project is a Windows application.

Step #3: Project Outputs



Here you must select the project outputs you wish to include in your installation package. For my project I select only 'Primary output', which includes the application DLL or EXE.



Step #4: Files to include



Here you have the opportunity to add additional files, like guides, HTML pages or just a ReadMe file. I will add just a ReadMe file:



Step #5: Confirmation



Here you can see the settings for the project that will be created. If you find a mistake or something, you can easily go back and change a specific setting.

6. If the project was successfully created, you will see this:



7. Now you can customize the setup project properties. To access the project properties grid, click on Setup1 project in the 'Solution Explorer' window:

Here are the properties and a short explanation of what they do:

AddRemoveProgramsIcon - Specifies an icon to be diplayed in the Add/Remove Programs dialog.
Author - Specifies the name of the author of an application or component.
Description - Specifies a free-form description for an installer.
DetectNewerInstalledVersion - Specifies whether to check for newer versions of an application on the user's computer.
InstallAllUsers - Specifies whether the package is installed for all users or only the current user.
Keywords - Specifies keywords used to search for an installer.
Localization - Specifies the locale for string resources and the run-time user interface.
Manufacturer - Specifies the name of the manufacturer of an application or component.
ManufacturerUrl - Specifies a URL for a Web site containing information about the manufacturer of an application or component.
PostBuildEvent - Specifies any commands to execute after the build ends.
PreBuildEvent - Specifies any commands to execute before the build starts.
ProductCode - Specifies a unique identifier for an application.
ProductName - Specifies a public name that describes an application or component.
RemovePreviousVersions - Specifies whether an installer will remove previous versions of an application or component.
RunPostBuildEvent - Specifies the condition under which the post-build event runs.
SearchPath - Specifies the path that is used to search for assemblies, files or merge modules on the development computer.
Subject - Specifies additional information describing an application or component.
SupportPhone - Specifies a phone number for support information for an application or component.
SupportUrl - Specifies a URL for a Web site containing support information for an application or component.
TargetPlatform - Specifies the target platform of the installer.
Title - Specifies the title of an installer.
UpgradeCode - Specifies a shared identifier that represents multiple versions of an application or component.
Version - Specifies the version number of an installer, merge module, or .cab file.

8. You can also specify what folders to create on the desktop and in the Start menu:



9. You can also customize the entries that will be added to the registry:





10. You can also customize the file types on the target machine:





11. You can also customize the user interface of the installer:





You can add additional dialogs:



12. You can also customize the custom actions:





13. You can also customize the launch conditions:





14. When you're done with project customizations, build the project (right click on 'Setup1', then select the 'Build' option):



Now you've got a new installation package for your application or component.

This tutorial showed the basics of creating a setup project, so now you can easily deploy your applications to the end-user.

Hi,
I want to add flash player setup along with .net application.
how to do ut.
Thank you,
avinash

Hi,

We could add Flash files as we do other files, however my concern is I want to put restriction on direct running of programs from programfiles folder where deployed files have been copied after setup or installation. I.e. I dont want user to copy my files from program files and paste it on another machine and run my flash files which we can consider as piracy or multiplying users with the cost of only one! Could you please help me on this?

Thanks
Laxman.

Hi, nice tutorial, but have you got a download link for the application, or do you have to buy it?

this is not an APP, do it with Visual Studio ..

Good morning friend!
I follow the tutorial and works exactly how you said... but I have a question... how can I make the .NetFramework be installed direct from my application cd, instead download from microsoft?

Great tutorial. I'll be sure to follow this when making an installer for my future softwares.

Thanks!

Can you configure the project so that everytime the application starts it will check for a newer version, similar to a click once deployment?

I'm trying to add a custom Form in my Setup Project. First, I referenced the Form project output in my setup project, then added this ouput to the customAction Install. But I never see the form when I execute my setup project. I tried to wrap the form in a custom class derived from Installer. then done with the wrapper class the same thing I did with the form. Same result. I must have missed something like setting a property in my setup project or maybe an attribute in my my class derived from Installer.
It seems to me like a very common requirement so if somebody could give me a hint.
I found the answer there : http://msdn.microsoft.com/en-us/library/d9k65z2d(VS.80).aspx
but it's rather odd (to say the less) that the project output must be in the Install and the Commit custom action to be activated
And you must add [RunInstaller(true)] attribute to your Installer derived class

This post has been edited by kekranx: 26 Aug, 2009 - 06:25 AM

Any chance you would reupload the images.

I cant see them.

Cheerss

There must be something wrong with your browser then, these images appear just fine. They are standard .jpg files.