Re: Deployment Strategies
Brian Vallelunga <[email protected]>
| Newsgroups | gmane.comp.windows.devel.dotnet.web |
|---|---|
| Message-ID | <[email protected]> |
This would be a really great plan if it weren't impossible for us. Our sites are updated almost constantly with very few scheduled large releases. I think we could use something more along the lines of a continuous integration and deployment system. What about other people out there? Brian -----Original Message----- From: Discussion of building .NET applications targeted for the Web [mailto:[email protected]] On Behalf Of Lizet Pena de Sola Sent: Tuesday, February 13, 2007 9:21 AM To: [email protected] Subject: Re: [DOTNET-WEB] Deployment Strategies We usually build set up projects for the projects in the solution. The deployment team in our case has nothing to do with the developers, and the developers do not have access to the production servers. So in order to make the deployment process easier and painless, we create a set up project for every project that needs to be elevated individually. For instance, one for the web services project, another one for the web project, another one for the intranet web project, etc. It mainly depends on where these projects will be deployed. When we create the build that will be elevated we label the files on that version in the source control system as, for instance, "deployed in V1.2.3"... Hope this helps, Lizet =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com