c# - How to make a setup installer? For asp.net mvc 2.0, cmd line applications and webservices -

I wonder how I can create a setup project for each of these projects

• ASP
• C # CMD line
• Application C # Web service

I am using VS 2010 Ultimate and I know That's the free version of the gradient installed for the CMD line application that I can use at least. I am not sure about the other 2. I also know about the setup project which you can use. I need a lot more than basics, so I'm not sure how to do these things or not.

asp.net mvc 2.0 criteria

Free (I'm actually a You do not want to pay for the installer - you can list them only because I give them information).

Terms of Service

Ability to force a user to set some settings. Like connection string, smtp settings should therefore be able to type it through the setup wizard and web.config should be updated based on this.

When it installs the stuff, all for all C # code. Dll should be

C # CMD line criteria

1. All the above criteria
2. I'm not sure that this Can be done in code but I have an html file that contains a template for a message The path of this file is in web.config, so I need to set this path to a person to install it every time . I tried to put it in code but I did not know how to make it the right path in development and the right path in production. It seems that if you are VS If you walk in, the path is different.

Web-Service

from the very first 2

thanks

If I were you, then I have a forum for some of your installers for some installations:

< Ul>

It is XML-based, which is conducive to source control, separately and merged

It has a rich set of tools for most of the scenarios

It's free and open source

This product-ready

It is used to make installation for products like Microsoft Office MS Office <

It has a rich community of Vix-users @lists. Sourceforge.net and StackOverflow

This VS

It is suited to build engines like NAnt and MSBuild

The VS setup project is not my choice because:

• It is very limited in the set of features -
• It encourages bad behaviors like installer classes
• Finally, by Microsoft
< / Ul>

Although I'm not familiar with InstallShield Limited Edition though.

Hope this observation will help you find the best option for your case.