Chris Arnold
Reputation: 5753
Website Build and Release Strategy
We have an ASP.Net MVC solution built in VS2008 and TFS2008. We use TFS Build and use Continuous Integration.
We have a deployment pipeline that enables us to progress a build, eventually, to our live site...
- Internal Dev (immediate deployment following a build)
- External Dev (used by internal testers to make sure it works on the production server)
- External Test (used by our client to test themselves)
- Live (self explanatory).
I have 2 questions relating to this
- Which ones of these should be built in Debug and which in Release?
- How should I write my TFSBuild.proj files to cope with this strategy?
Upvotes: 0
Views: 270
Answers (1)
Mel Gerats
Reputation: 2252
As per your points, only the Internal dev should be in Debug mode. The External Dev should be in Release mode if you want to mimic the production environment
Upvotes: 2
Related Questions
- Help me come up with a deployment strategy
- Coming up with a better ASP.NET deployment strategy
- Automated Deployement of ASP.Net MVC Website In IIS server with a Continuous Deployment
- Continuous Deployment Approach for on premiss Asp.Net-MVC
- Automated Deployment and Upgrade Strategy for ASP.Net MVC Application
- Best practice for deploy website
- Looking for a good web application deployment strategy (ASP.NET MVC3)
- What's the best deployment strategy for ASP.NET
- Automate deployment of asp.net mvc site
- WebSite Deployment Skills