TFS 与 SVN [英] TFS vs SVN
问题描述
我即将开始一个项目 (.NET)，需要在 TFS 和 SVN 之间做出决定.
I am about to start a project (.NET) and need to decide between TFS and SVN.
我更习惯于 SVN(带乌龟客户端)、CVS 和 VSS.TFS 是否具有 SVN 中可用的所有功能
I am more used to SVN(with tortoise client), CVS and VSS. Does TFS have all features available in SVN
有没有人从 SVN 切换到 TFS 并觉得值得?
此外，如果我们需要使用 TFS，我们可能需要 Visual Studio.
Have any of you switched from SVN to TFS and found it worthwhile?
Also it looks like we may need Visual Studio if we need to work with TFS.
金钱不是考虑因素，因为我们已经拥有 TFS 的许可证.而且我对TFS vs SVN的Source Control特性更感兴趣，当然也欢迎其他特性列表.
Money is not a consideration since we already have the licenses for TFS in place.
And I am more interested in the Source Control features of TFS vs SVN, of course other features list is also welcome.
推荐答案
嗯，对我来说，选择显然是 TFS :
Well, to me, the choice is obviously TFS :
SVN 集成到 Visual Studio 中至少可以说是不完整的(IDE 中没有很多功能)，并且有点错误(AnkhSVN 肯定是)，而 TFS 是完美的(这是有道理的)……).我的整个工作区使用 SVN(一个月内)多次损坏，从未使用 TFS(大约 2 年)
SVN integration into Visual Studio is incomplete to say the least (a lot of features aren't available from the IDE), and a bit buggy (AnkhSVN certainly is), while TFS one is perfect (which makes sense...). I've had my whole workspace corrupted several times using SVN (during one month), never using TFS (aprox 2 years)
虽然两个系统的 Source-Control 相关功能可能相当，但它们可以通过 TFS 直接从 IDE 访问，而您必须依赖 TortoiseSVN 或其他外部工具(如果您使用 SVN).在解决方案资源管理器选项卡上点击几下即可访问几乎所有 TFS 任务.
While Source-Control related features of both systems are probably quite equivalent, they are accessible directly from the IDE with TFS, while you have to rely on TortoiseSVN or other external tools if you use SVN. Almost all TFS tasks are accessible in a few clicks on the solution explorer tab.
使用 TFS 进行合并要容易得多，即使对于复杂的合并(例如，SVN 会添加 <<<<<<'s 和 >>>>>>>>>'s 到您的 .csproj 文件，因此您需要手动编辑它们以从 VS 再次打开它们.)
Merging is a lot easier with TFS, even for complex merges (for example, SVN will add <<<<<<'s and >>>>>>>>>'s to your .csproj files, so you'll need to manually edit them to open them again from VS.)
虽然我认为这些原因足以让我更喜欢 TFS 而不是 SVN，但我必须补充一点:
While I think those reasons are more than enough to prefer TFS over SVN, I mus add that :
TFS 不仅仅是一个源代码控制工具(想想工作项、项目门户等)
TFS is more than just a source-control tool (think work items, project portal, etc.)
我过去曾在一个中型项目(12 名编码员、3 名测试员、3 名业务分析师)中使用过它，我们已经能够成功地将 TFS 中的所有任务(错误报告、项目文档、构建过程等)
I've used it on a medium-sized project (12 coders, 3 testers, 3 business analysts) in the past, and we've been able to successfully centralize all the tasks in TFS (bug reports, project documentation, build process, etc.)
我并不是说使用 SVN 和其他第三方工具做同样的事情是不可能的，但是将所有东西很好地集成到一个产品中绝对是件好事.
I'm not saying it's not possible to do the same using SVN and other third-party tools, but it's definitely nice to have all things nicely integrated in one product.
为了公平起见，以下是 TFS 的两个明显缺点:
To stay fair, here are the two obvious drawbacks of TFS :
它的价格
Its price
安装 TFS 相当痛苦，而安装 SVN 只需几分钟.
Installing TFS is quite a pain, while SVN installation is a matter of minutes.
在 SqlServer 2008 上安装 TFS 2008 相当复杂，你不能在 PDC 等上安装 TFS.对我来说，这绝对是我使用 Microsoft 产品时遇到的最糟糕的安装体验.
Installing TFS 2008 over SqlServer 2008 is quite complicated, you cannot install TFS on a PDC, etc. To me, it's definetely the worst installation experience I've ever had with a Microsoft product.
话虽如此，一旦安装，TFS 非常易于使用(特别是对于不熟悉源代码控制系统的编码人员)
That being said, once installed, TFS is very easy to use (especially for coders not familiar with source control systems)
在我目前的项目中，我从 SVN 开始，然后迅速切换到 TFS.我很高兴我做到了.
我决定切换的主要原因显然是 SVN 的整体错误行为(我使用的是 VisualSVN 作为服务器，AnkhSVN 作为客户端).每周至少有一次，我发现自己在神秘的 AnkhSVN 错误消息上花费数小时.
The main reason why I've decided to switch is clearly the overall buggy behaviour of SVN (I was using VisualSVN as a server and AnkhSVN as a client). At least once a week, I found myself spending hours on cryptical AnkhSVN error messages.
迄今为止，我还没有找到任何理由让我后悔改用 TFS.
To date, I haven't found a single reason to regret the switch to TFS.
这篇关于TFS 与 SVN的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
