TFS VS 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和发现它值得吗？
此外看起来我们可能需要Visual Studio，如果我们需要与TFS工作。
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，当然其他的功能列表也是值得欢迎的。
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)
虽然两个系统的源代码控制相关的功能可能相当相当，他们是直接从与TFS的IDE访问，而你不得不依赖的 TortoiseSVN的或者如果您使用SVN其他外部工具。 几乎所有的TFS任务是在Solution Explorer标签上点击几下访问。
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将添加＆LT;＆LT;＆LT;＆LT;＆LT;＆LT;公司及>>>>>>>>>'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.)
虽然我认为这些理由足够多的preFER 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 codeRS，3测试仪，3个业务分析人员），在过去，我们已经能够成功地集中TFS中的所有任务（bug报告，项目文档，构建过程等）
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.
安装TFS 2008在SqlServer的2008年是相当复杂的，你不能在PDC等。要我安装TFS，它是definetely最糟糕的安装经验，我曾经有过一个微软的产品。
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是非常容易使用（尤其是codeRS不熟悉的源代码控制系统）
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的作为客户端）。每周至少一次，我发现自己花费大量时间在cryptical 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 VS SVN的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
