步骤一步ASP.NET自动生成/部署 [英] Step-By-Step ASP.NET Automated Build/Deploy
问题描述
好像有自动化人的构建/部署变得难以通过所有的人在网络上的教程支持不同的情况来分析的这么多不同的方式。所以我想present问题的计算器人群......这将是使用以下配置来设置自动构建和部署系统的最佳方式：
Seems like there are so many different ways of automating one's build/deployment that it becomes difficult to parse through all the different scenarios that people support in tutorials on the web. So I wanted to present the question to the stackoverflow crowd ... what would be the best way to set up an automated build and deployment system using the following configuration:
- Visual Studio 2008中
- Web应用程序项目
- CruiseControl.NET
其中的第一件事情我想是有CCNET自动压缩输出，并将其复制到服务器，但需要手工作业目的地解压。但是，如果我们试图把所有的文件逐个复制，那么它可能需要很长的时间，如果它是一个大的应用程序（建立在我们的办公室的数据中心外部服务器的生活......我知道）。
One of the first things I tried was to have CCnet automatically zip the output and copy it to the server, but then that requires manual work to unzip at the destination. However, if we try to copy all the files individually, then it could potentially take a long time if it's a large application (build server lives outside of the datacenter in our office ... I know).
也特别感兴趣的是我们如何支持多种环境，因为我们有开发，QA，用户验收测试，然后当然PROD的。
Also of particular interest is how we would support multiple environments as we have dev, qa, uat, and then of course prod.
<一个href=\"http://blogs.iis.net/msdeploy/archive/2008/01/22/welcome-to-the-web-deployment-team-blog.aspx\">MSDeploy看来真的很有趣，但除非我间$ P $错误pting文献中，不从构建服务器的部署输出的情况下提供帮助。如果有的话，它看起来像它会在整个构建农场部署一台构建有用......但即使是从一个环境到另一个部署，人们必须手动更改配置设置和Web服务URL等。
MSDeploy seems really interesting, but unless I'm interpreting the literature incorrectly, doesn't help in the scenario of deploying from the output of a build server. If anything, it seems like it'll be useful in deploying one build across a build farm ... but even for deploying from one environment to another, one would have to manually change config settings and web service URLs, etc.
推荐答案
最近，我花了几天就在我的公司部署自动化的工作。
I recently spent a few days working on automating deployments at my company.
我们使用CruiseControl的，楠，MSBuild的组合来生成应用程序的发布版本。随后单独的脚本使用MSDeploy和的XCopy备份直播网站，并在传输的新文件。
We use a combination of CruiseControl, NAnt, MSBuild to generate a release version of the app. Then a separate script uses MSDeploy and XCopy to backup the live site and transfer the new files over.
我们的解决方案是在答案简要描述这个问题<一href=\"http://stackoverflow.com/questions/45783/automate-deployment-for-web-applications\">http://stackoverflow.com/questions/45783/automate-deployment-for-web-applications
Our solution is briefly described in an answer to this question http://stackoverflow.com/questions/45783/automate-deployment-for-web-applications
这篇关于步骤一步ASP.NET自动生成/部署的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
