至于与 Visual Studio 的集成，Team Explorer for TFS 是无可比拟的。不过，我已经将 Anhk 与 SVN 结合使用，效果也很好。我想剩下的内容已经说过了:-)
希望这会有所帮助。
Better is a big discussion, but along the same lines you have to factor in cost.
SVN is free, where as TFS isn't. However; if you have your Visual Studio through an MSDN subscription and this is of high enough level, then you will get TFS2010 for free through your MSDN subscription downloads when released. This may be a factor which tips the balance.
As for the integration with Visual Studio, you can't beat Team Explorer for TFS. However, I have used Anhk with SVN and that works well too. I think the rest of this has been said :-)
The question is rather old, however in case someone stumbles on it: since January 2013, git has been integrated into TFS (announcement: http://www.visualstudio.com/en-us/news/2013-jan-30-vso#git support). What it means is that the team can now use git as the source control tool (instead of, but not alongside, the "built-in" TFS version control system) while still using the rest of TFS for activities such as continuous integration, issues tracking, and so on.
I can only speak to Visual Studio integration for SVN. I've used both VisualSVN and AnkhSVN. They both have pretty tight integration and allow you to perform various operations from the Solution Explorer menu the way you would have normally done it with VSS. Version 2+ of Ankh (one I currently use) has been very stable for me and worlds better than the older versions.
This is in addition to the other answers, not a full answer as Michael Shimmins satisfied most of what I would say
TFS (especially 2010) is incredibly approachable for implementing source control techniques that you would have been terribly hard-pressed to execute with VSS. Branching and merging is much easier with TFS than SVN to start and follow over time. I would say the same thing about Git from an user interaction perspective, but those tools are getting better slowly.
Git is a great tool if you spend the ramp up time and the techniques that community take as standard practice are well worth the effort in any version control system. You're still going to run into conflicts with SLN and CSProj/VBProj files in teams of > 2. This is a result of the way those files are structured and managed.
发布评论
评论（5）
TFS 是一个应用程序生命周期管理解决方案，SVN 和 Git 仅是源代码控制。
以及问题跟踪、文档管理、报告、持续集成、测试虚拟实验室等。
TFS 进行源代码控制 SVN 是集中式源代码控制，Git 是分布式的。
Stackoverflow 上有很多关于 TFS 与 SVN 的讨论。
TFS 与 Visual Studio 的集成最为紧密。
SVN 有一些第三方选项可用于集成到 Visual Studio 中，它们非常好，但不如 TFS 紧密集成。
Git 具有 GitExtensions，它允许在 Visual Studio 中进行低级别的集成。
TFS is an Application Life-cycle Management solution, SVN and Git are source control only.
TFS does source control as well as issue tracking, document management, reporting, continuous integration, virtual labs for testing etc.
TFS's Source Control & SVN are centralized source control, Git is distributed.
There have been many discussion on Stackoverflow about TFS vs SVN.
TFS is the most tightly integrated into Visual Studio.
SVN has a few third party options for integrating into Visual Studio and they are quite nice, but not as tightly integrated as TFS.
Git has GitExtensions which allows for a low level of integration within Visual Studio.
更好的是进行大讨论，但同样，您必须考虑成本。
SVN 是免费的，而 TFS 则不是。然而;如果您通过 MSDN 订阅获得了 Visual Studio，并且这是 高足够级别，那么您将在发布时通过 MSDN 订阅下载免费获得 TFS2010。这可能是一个打破平衡的因素。
至于与 Visual Studio 的集成，Team Explorer for TFS 是无可比拟的。不过，我已经将 Anhk 与 SVN 结合使用，效果也很好。我想剩下的内容已经说过了:-)
希望这会有所帮助。
Better is a big discussion, but along the same lines you have to factor in cost.
SVN is free, where as TFS isn't. However; if you have your Visual Studio through an MSDN subscription and this is of high enough level, then you will get TFS2010 for free through your MSDN subscription downloads when released. This may be a factor which tips the balance.
As for the integration with Visual Studio, you can't beat Team Explorer for TFS. However, I have used Anhk with SVN and that works well too. I think the rest of this has been said :-)
Hope this helps.
这个问题相当老了，但是万一有人偶然发现它：自 2013 年 1 月以来，git 已集成到 TFS 中（公告：http://www.visualstudio.com/en-us/news/2013-jan-30-vso#git 支持）。这意味着团队现在可以使用 git 作为源代码控制工具（而不是“内置”TFS 版本控制系统，但不能与它一起使用），同时仍然使用 TFS 的其余部分来进行持续集成、问题等活动。跟踪等。
MSDN 上的原始讨论：http://blogs.msdn.com/b/visualstudioalm/archive/2013/01/30/getting-started-with-git-in-visual-studio-and -team-foundation-service.aspx
StackOverflow 有大量相关讨论 (https://stackoverflow.com /search?q=tfs+git)，无法指向任何特定内容。
The question is rather old, however in case someone stumbles on it: since January 2013, git has been integrated into TFS (announcement: http://www.visualstudio.com/en-us/news/2013-jan-30-vso#git support). What it means is that the team can now use git as the source control tool (instead of, but not alongside, the "built-in" TFS version control system) while still using the rest of TFS for activities such as continuous integration, issues tracking, and so on.
Original discussion on MSDN: http://blogs.msdn.com/b/visualstudioalm/archive/2013/01/30/getting-started-with-git-in-visual-studio-and-team-foundation-service.aspx
StackOverflow has a large set of relevant discussions (https://stackoverflow.com/search?q=tfs+git), cannot point to anything specific.
我只能谈论 SVN 的 Visual Studio 集成。我使用过 VisualSVN 和 AnkhSVN。它们都具有非常紧密的集成，并允许您从“解决方案资源管理器”菜单执行各种操作，就像通常使用 VSS 执行操作一样。 Ankh 的 2+ 版本（我目前使用的一个）对我来说非常稳定，并且比旧版本更好。
这看起来像是关于使用 Git 与 Visual Studio 的相当详细的讨论。
I can only speak to Visual Studio integration for SVN. I've used both VisualSVN and AnkhSVN. They both have pretty tight integration and allow you to perform various operations from the Solution Explorer menu the way you would have normally done it with VSS. Version 2+ of Ankh (one I currently use) has been very stable for me and worlds better than the older versions.
This looks like a fairly detailed discussion of using Git with Visual Studio.
这是对其他答案的补充，而不是完整的答案，因为 Michael Shimmins 满足了我所说的大部分内容，
TFS（尤其是 2010）对于实现源代码控制技术非常容易实现，而使用 VSS 来执行这些技术是非常困难的。随着时间的推移，使用 TFS 比 SVN 更容易启动和跟踪分支和合并。从用户交互的角度来看，我对 Git 也有同样的看法，但这些工具正在慢慢变得更好。
如果您花费了一些时间来学习，Git 是一个很棒的工具，并且社区将其作为标准实践的技术在任何版本控制系统中都非常值得付出努力。在 > > 的团队中，您仍然会遇到与 SLN 和 CSProj/VBProj 文件的冲突。 2. 这是这些文件的结构和管理方式的结果。
This is in addition to the other answers, not a full answer as Michael Shimmins satisfied most of what I would say
TFS (especially 2010) is incredibly approachable for implementing source control techniques that you would have been terribly hard-pressed to execute with VSS. Branching and merging is much easier with TFS than SVN to start and follow over time. I would say the same thing about Git from an user interaction perspective, but those tools are getting better slowly.
Git is a great tool if you spend the ramp up time and the techniques that community take as standard practice are well worth the effort in any version control system. You're still going to run into conflicts with SLN and CSProj/VBProj files in teams of > 2. This is a result of the way those files are structured and managed.