Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • 1
    The main issue, I believe, is that for Production deployments, the build process and the deployment process should be completely separated. If not then you are building new assemblies (which have not been tested) to deploy into production. Commented Feb 15, 2012 at 16:31
  • @MichaelChatfield - You could set it up that way. We have to do new builds each time since part of our deployment is an ancient VB6 program that won't get it's references right if we do it any other way. Commented Feb 15, 2012 at 16:48