SVN或TFS的部署解决方案
ASP.NET 开发。
工作站操作系统：Win XP
网络托管操作系统：Win server 2003
我正在寻找源代码控制+部署解决方案。有些人使用 Mercurial (TortoiseHG + Visual Studio 插件) & 开始。我想知道是否有适合 SVN 或 TFS 的好捆绑包。由于TFS已经集成在Visual Studio中，所以我只需要一个部署工具。而对于SVN，我需要VS插件和部署工具。对于部署工具，希望它像GO一样，具有一键点击部署的能力。社区可以推荐一些流行的或工业标准设置吗？谢谢。
ASP.NET development.
workstation OS: Win XP
web hosting OS: Win server 2003
I am looking for a source control + deployment solution. Some people use
Mercurial (TortoiseHG + Visual Studio plugin) & GO. I was wondering if there's a good bundle for SVN or TFS. Since TFS is already integrated in Visual Studio, I just need a deployment tool. While for SVN, I need both VS plugin and deployment tool. For deployment tool, hope it's like GO, has one button click to deploy capability. Can the community recommend some popular or industrial standard setup? Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果您只是使用 ASP.NET 脚本，那么您只需将 SVN 文件检出到 Web 服务器上，将它们安装到正确的位置，然后只需在 Web 服务器上运行“svn update”即可更新所有文件服务器。简单又容易。另一种方法是通过将文件从存储库导出到服务器来覆盖服务器文件，以使其保持最新。第一种方法的优点是仅传输更改的文件，因此速度很快。
如果您想走完整部署路线，GO 是一个选择，还有许多其他 ALM 产品可供选择。
所有这些的替代方法是使用持续集成构建服务器，例如 Hudson。 Hudson 可以在签入后进行构建并保留“工件”（即版本包），然后可以使用类似 部署插件。
顺便说一句，没有任何东西具有“一键部署功能”，您将花费数周甚至数月的时间将其全部设置正确，然后不对代码执行任何操作否则您将不得不返回并进行更多设置和配置。这些东西确实很有用，但它们并不是解决发布管理中遇到的任何问题的简单选择。
if you're just using ASP.NET scripts, then you can simply install them to the right place by doing a checkout of your SVN files onto the web server, and then can update all the files by just running 'svn update' on the server. Simple and easy. An alternative is to overwrite the server files by exporting the files from the repo onto the server to keep them up to date. The first way has the benefit of only transferring changed files so its quick.
If you want to go the full-deployment route, GO is an option and there are plenty of other ALM products to choose from.
An alternative to all that is to use a continuous-integration build server, like Hudson. Hudson can build after checkins and keep 'artifacts' (ie packages of releases) that can then be deployed using something like deployment plugin.
BTW, there is nothing that has a 'one-click to deploy capability' you will spend weeks, if not months, getting it all set up just right, and then don't do anything to your code or you'll have to go back and do some more setting up and configuration. These things can be really useful, but they are not easy options to solve whatever problems you have with release management.