ASP.NET：我有哪些部署选项？
我很快将管理一组 ASP.NET Web 服务器...
部署 ASP.NET Web 服务器有哪些技术限制？我可以复制文件，重新启动网站，然后就可以了吗？
这和VS2010的“部署”有什么不同吗？
我拥有什么“类型”的项目重要吗：网站还是 Web 应用程序？
I'll soon be managing a fleet of ASP.NET webservers...
What are the technical limitations with deploying an ASP.NET webserver? Can I just copy the file(s) over, restart the website, and I'm good to go?
Is this any different than what VS2010's "deploy" does?
Does it matter what "type" of project I have: a Web Site or a Web Application?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您可能需要查看 适用于 Visual Studio 的 Web 部署项目 (WDP)。这些是 MSBuild 类型的项目，将 aspnet_compile.exe 的功能包装到一组易于配置的项目属性中。如果您正在进行自动化构建和部署，这些类型的项目会让事情变得更加简单（至少它们对我来说是这样！）。
它们使您能够根据构建类型（发布、调试等）交换配置文件（appSettings、connectionStrings 等），并且您还可以设置输出 DLL 的构建方式（每个文件、一个装配等）。这对于网站应用程序非常有用，但对于 Web 应用程序项目则不太有用。
如果您混合使用 WSP 和 WAP，则使用 WDP 可能会带来一定的一致性。
查看 Scott Guthrie 关于使用 WDP 的博客还有他的 VS2010 更新。
You may want to check out Web Deployment Projects (WDP) for Visual Studio. These are MSBuild-type projects that wrap functionality of aspnet_compile.exe into an easily configurable set of project properties. If you're doing automated builds and deployments, these types of projects make thing a lot simpler (at least they did for me!).
They provide you with the ability to swap out configuration files (appSettings, connectionStrings, etc.) depending on the type of build (Release, Debug, other) and you can also set how you want your output DLL's built (per-file, one assembly, etc.). This is very useful for web site applications -- not so much for web application projects.
If you have a mix of WSP's and WAP's, using WDP's may give you some consistency.
Check out Scott Guthrie's blog on using WDP's and also his VS2010 update.
网站或 Web 应用程序并不重要。这只是网站开发和编译时的区别，而不是部署时的区别（网站将有更多 .dll 文件除外）。
您实际上可以将所有文件复制到新网站，只要当你正在做一个干净的副本时。该应用程序将自动重新启动，因此您不必重新启动网站。
为了使事情变得更容易，我将使用自动发布器，例如 NaNT、Cruise control 或 MSBuild。我从未使用过它，但 VS2010 的内置发布器也可能满足您的需求。
Web site or Web application doesn't matter. That is just a distinction that is made when the site is developed and compiled, not when it's deployed (except a web site will have more .dll files.)
You really can just copy all of the files over to your new website, as long as you are doing a clean copy. The application will automatically re-jit, so you don't necessarily have to restart the website.
To make things much easier, I would use an automated publisher, such as NaNT, Cruise control, or MSBuild. I've never used it, but the built in publisher from VS2010 may also give you what you need.