Git / SVN的asp.net开发，而不是VSS？ [英] Git/SVN for asp.net development instead of VSS?

问题描述

在工作中，我们正在使用ASP.net 2.0和VSS。 VSS是一个野兽，我们一直在检查文件的人有问题，并没有分支 - 让它发疯。我知道SVN / GIT主要由开源开发人员使用，ASP.NET开发人员使用它有什么缺点？我一直在内部推动SVN，但我认为GIT可能也是一个很好的选择。我们的团队分布在3大洲。

解决方案

我之前在公司环境中使用过Subversion，取得了巨大成功。我没有亲自在公司环境中使用过Git，但是分布式办公室听起来很合适。

当每个人都赶上速度的时候，预计会有一个很大的驼峰 ，但是离开VSS绝对是一个好主意。当我们从VSS转移到SVN时，我们从未回头过。我会鼓励你不要吝啬对新系统的培训。让一些聪明的人阅读你选择的任何系统的文档 - 并且彻底阅读 。然后弄清楚你将如何使用它并进行适当的沟通。建议其他人真正需要的文档中的哪些部分需要使用，并给他们足够的时间来阅读它。源控制不应该在新闻回报和希望的基础上完成：）

At work, we are using ASP.net 2.0 and VSS. VSS is a beast, we are continually having issues with people checking out files and there is no branching - makes it crazy. I know SVN/GIT is mainly used by open source developers, are there any downsides to ASP.NET developers using it? I have been pushing for SVN internally, but am thinking GIT might also be a great option. Our team is spread across 3 continents.

解决方案

I've used Subversion in a corporate setting before with great success. I haven't personally used Git in a corporate environment, but with distributed offices it sounds like a good fit.

Expect a big "hump" while everyone gets up to speed, but moving off VSS is definitely a good idea. We never looked back when we moved from VSS to SVN. I would encourage you not to skimp on training up on the new system. Get a few smart folk to read the documentation for whichever system you pick - and read it thoroughly. Then work out how you're going to use that, and communicate that appropriately. Suggest which bits of the documentation everyone else really needs to use, and give them enough time to read it. Source control shouldn't be done on a "press return and hope" basis :)

这篇关于Git / SVN的asp.net开发，而不是VSS？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！