Geek Answers Handbook

The best way to deploy a VS-2008 web project

What is the preferred method for deploying a web project? Just copy the dll after compilation in release mode and register them? or using NSIS to build an installer or project configured by MS.

+3
source share
4 answers

I usually use the Web Deployment Project for each WebSite or WebApplication, it allows me to manage assembly configurations, merge, and define the pre-assembly MSBuild Tasks.

You can also take a look at the Microsoft Web Application Installer , it will be very good, but it is still in beta testing, however you can try ...

+5
source

It depends a lot on where your website is going and what experience you want to provide. If you are deploying to web hosting, it is best to use xcopy for deployment and documentation. If you have a real end system, the easiest way is to create an installer to do all the leg work for your customers and possibly save your work with some documents.

+1
source

I would recommend investing in setting up a continuous integration process (CruiseControl.Net or TeamCity, etc.). Since you are probably not only going to deploy it for your client only once.

One-click auto deployment - Godsend. If you invest for several days, you can automatically deploy the dev environment every time someone checks the code (and it compiles and all the tests pass), configures the deployment to the test environment daily and has a button for automatic deployment whenever you want.

0
source

Andreas, I'm going to get CC.Net. At the same time, I am using a web deployment project. Using this and going through the setup, he creates the "release" folder, which contains the folder with the bin folder, as well as aspx in the parent folder.

I assume that I can now create the MSI file using the "release" folder or I need to do something else to create the MSI that I can run on the client server

0
source

More articles:


All Articles