由网友(该死的心动)分享简介：请参阅http://stackoverflow.com/questions/690766/vss-or-svn-for-a-net-project,其中包括许多其他类似的问题。Seehttp://stackoverflow.com/questions/690766/vss-or-svn-for-a-net-projec...

请参阅   http://stackoverflow.com/questions/690766/vss-or-svn-for-a-net-project,   其中包括许多其他类似的问题。

See http://stackoverflow.com/questions/690766/vss-or-svn-for-a-net-project, among many other similar questions.

有很多选择在那里的ASP.Net开发人员，有些是垃圾总量，有些是功能丰富的和昂贵的。

There are a lot of options out there for ASP.Net Developers, some are total garbage and some are feature rich and pricey.

我一直在使用Visual源安全2005年一段时间做个人发展的时候，但只有在我的个人项目。它有问题，让我说。

I've been using Visual Source Safe 2005 for a while when doing personal development, but only on my personal projects. It has issues, let me say.

最糟糕的问题是，它似乎并没有能够处理ASP.Net Web站点。大多数事情从来没有签出的编辑，无论你如何设置它的，我通常要获取最新的，并说保持局部的变化和退房来获得该功能。

The worst issue is that it doesn't seem to be able to handle ASP.Net Web Sites. Most things are never checked out on edit regardless of how you set it up and I usually have to Get Latest and say "Keep local changes and Check Out" to get that functionality.

不过，我想看看是否有人可以帮助我远离这个怪物的东西更稳定。 Team Foundation Server的显然是矫枉过正。 SourceVault是可靠的，但有点贵。 SVN是免费的，但所有的插件，大多数其他源代码控制给你做它的成本，当这一切都说过和做过东西。

Anyway, I wanted to see if anyone could help me move away from this monster to something more stable. Team Foundation Server is obviously overkill. SourceVault is reliable, but kinda pricey. SVN is free, but all of the plugins that most other source control providers give you make it cost "something" when it's all said and done.

我只是想知道大家都在用，如果他们能提出一个更好的路要走。

I was just wondering what everyone is using and if they can suggest a better way to go.

推荐答案

我最近用三个免费工具动了我的团队掉的SourceSafe到Subversion：

I recently moved my team off SourceSafe to Subversion using three free tools:

VisualSVN服务器 - Subversion服务器软件包为Windows TortoiseSVN的 - 资源管理器外壳扩展 AnkhSVN的 - Visual Studio的插件 VisualSVN Server - Subversion server package for Windows TortoiseSVN - Explorer shell extension AnkhSVN - Visual Studio plugin

您也想引用 Subversion书中。

这是很容易建立，并已取得巨大的成功。 SourceSafe是一场灾难 - 我的最后一根稻草是，当我不得不合并一个特性分支后发现该功能确实没有任何可用的形式存在。

This was easy to set up and has been a tremendous success. SourceSafe is a disaster -- the final straw for me was when I had to merge a feature branch and discovered that the functionality really doesn't exist in any usable form.

我preFER到使用TortoiseSVN进行复杂的操作，如添加的解决方案，SVN，分支和合并。我用AnhkSVN更新，提交和恢复。

I prefer to use TortoiseSVN for complex operations such as adding solutions to svn, branching, and merging. I use AnhkSVN for updates, commits, and reverts.

请注意，这些工具的最新版本目前正在针对不同版本的颠覆建成。的VisualSVN和AnkhSVN的构建针对1.5.5，但TortoiseSVN是建立针对1.6。你可以抓住的TortoiseSVN的previous版本或使用每日构建AnkhSVN的的。

Be aware that the latest versions of these tools are currently built against different versions of Subversion. VisualSVN and AnkhSVN are built against 1.5.5 but TortoiseSVN is built against 1.6. You can either grab the previous version of TortoiseSVN or use a daily build of AnkhSVN.