TFS对于大型团队高效，SVN对于小型团队高效吗？
我是开源和 SVN 爱好者。我们公司面临着必须在 SVN 或 Team Foundation Server 之间做出选择的情况。我试图说服其他人使用 SVN，因为我认为 TFS 在大型团队中得到了增强。我们只有 7 名开发人员和 3 名测试人员。我的说法正确吗？
I'm and open source and SVN lover. We at the company are at a situation that must decide between SVN or Team Foundation Server. I'm trying to convince others to use SVN because I think TFS is enhanced in large teams. We are just 7 developers and 3 testers. Am I right about this?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（7）
为什么你认为TFS是一个大系统？
我使用 SQL Express 将其安装在我的 Windows 7 笔记本电脑上，但我什至没有注意到它的存在。使用 TFS2010，您可以从一开始就选择不安装 Sharepoint、Reportign Services 和 Analysis 服务集成。您可以只拥有版本控制、工作项跟踪（错误、测试、问题、任务和用户故事）和自动构建。
事实上，我在 20 分钟内安装并配置了所有这些内容，而在我最近的项目中，大约花了 30 分钟才能设置包含所有这些内容的新产品。
为什么要使用 TFS？
如果您对 TFS 提供的基本安装感到满意，那么您可以如果您需要自动化环境测试，请添加实验室管理；如果您需要更多报告，请添加分析服务。
Why do you think that TFS is a large system?
I have it installed on my Windows 7 laptop using SQL Express and I do not even notice it is there. With TFS2010 you can opt not to install the Sharepoint, Reportign Services adn Analysis services integration from the get go. You can instead just have Version Control , Work Item tracking (Bugs, Tests, Issues, Tasks and User Storys) and automated Build.
In fact I installed and configured all of that in under 20 minutes and on my most recent project it took around 30 minutes to setup a new product with all of those things.
Why would you use TFS?
If you are then comfortable with what TFS is offering with a Basic install you can then add Lab Management if you want automated enviroment testing or Analysis services if you want more reporting.
嗯，TFS 不仅仅是版本控制。如果您只是寻求版本控制，TFS 就太昂贵了。恕我直言。我会坚持使用 SVN。但是，如果您正在寻找测试套件、问题管理等内容，那么我会研究 TFS。
Well, TFS is much more than version control. If you are looking for just version control, TFS is way too expensive. IMHO. I would stick with SVN. However if you are looking for things such as the test suite, issue management, etc, then I would look into TFS.
我不确定两者之间是否存在任何内在差异（就团队规模而言）。我知道的最大区别是：
I'm not sure there's any inherent difference (with respect to team size) between the two. The big differences that I'm aware of are:
比较 SVN 和 TFS 就像比较苹果和橘子。 SVN 是一个修订控制系统，而 TFS 是一个 ALM 平台，就像其他人已经提到的那样。
假设一家公司选择 Subversion、CruiseControl.NET、某种敏捷项目管理工具、错误跟踪器（Bugtracker.NET、Bugzilla，...）。假设这家公司选择的所有工具都是OSS，人们会认为它是免费的，对吧？不幸的是，您仍然需要开始集成所有这些工具，这才是真正的成本所在。
当然，像 Team Foundation Server 这样的平台会产生许可成本，并提供前面提到的所有 OSS 工具所提供的功能，但已经很好地集成了。
因此，基本上，如果您想要的是支持 ALM 的工具，并且您是面向 Microsoft 的，那么您应该认真考虑将 TFS 作为一种选择。当然，作为一名技术人员，弄清楚如何将 Bugzilla 与 Subversion 和项目管理工具集成是很有趣的，并且花几个晚上试图弄清楚我们如何将所有数据导出/导入到专门开发的定制开发的报告工具中。人力资源部门的时间跟踪报告等等。你明白我的意思。
最后，OSS 替代路径的成本比 TFS 路径高得多，人们只是不愿意承认这一点，另一方面，当然，如果您想要的只是修订控制系统，则不需要 TFS。但如果这就是您作为开发人员所需要的一切，您可以称自己为认真的开发人员吗？ ;-)
Comparing SVN to TFS is like comparing apples and oranges. SVN is a Revision Control system whilst TFS is an ALM platform like others have already mentioned.
Lets assume that a company chooses for Subversion, CruiseControl.NET, some kind of Agile Project management tool , a bug tracker (Bugtracker.NET, Bugzilla, ...). Let's assume that all the tools that this company chooses is OSS, one would think that it's free, right? Unfortunately, you would still need to start integrating all these tools and that is where the real cost is.
Sure, a platform such as Team Foundation Server comes with a licensing costs and offers what all the previously mentioned OSS tools offers too but already nicely integrated.
So basically if what you want are tools to support your ALM and you are Microsoft-oriented you should seriously consider TFS as an option. Sure as a technical guy it is fun figuring out how to integrate Bugzilla with Subversion and the project management tool, and the spending nights trying to figure out how we export/import all that date into the custom developed reporting tool that has been specially developed for the HR department for the time tracking reports, and so on. You understand what I mean.
In the end the OSS alternative path costs so much more than the TFS path and people just don't like to admit it, on the other hand off course, if all you want is a Revision Control System you don't need TFS. But if that is all you need as a developer, can you call yourself a serious developer? ;-)
我见过 SVN 在自动构建服务器等支持下成功地在非常大的团队中使用。如果您试图说服其他人使用 SVN，您可能最好只找出 TFS 所没有的您喜欢 SVN 的 3 个原因以及为什么您认为这些原因很重要，而不是试图笼统地说一个“更高效” ”
I've seen SVN used successfully with very large teams, when backed by things like automated build servers. If you're trying to convince others to go with SVN, you are probably better off just identifying the 3 reasons you love SVN that TFS doesn't have and why you feel those are important, than trying to broadly say one is "more efficient"
+2 美分。
TFS 不仅为您带来源代码控制 + 工作项跟踪（错误、测试、问题、任务和用户故事）+ 自动构建，您还可以获得一个非常大且令人印象深刻的分析数据库，您可以在其中交叉来自这些不同数据源的信息，而无需额外的工作。我的意思是，您可以看到为什么特定构建有一些错误，与已签入的指定文件相关，与文件相关的任务/错误相关，与与任务相关的用户故事相关，等等。无需额外的努力，您就可以更详细地了解开发项目中“正在发生的事情”。
+2 cents.
TFS not only brings you Source Control + Work Item tracking (Bugs, Tests, Issues, Tasks and User Storys) + automated Build, you also get a VERY BIG AND IMPRESSIVE Analysis Databse in which you can cross information from these different data sources, without extra work. I mean, you can see why a specific build has some bugs, related to the specified files that have benn checked in, related to the tasks/bugs related to the files, related to the user story which is related to the task, etc. Without additional effory you can get a more detailed view of "what's happening" in a development project.
如果您想了解 TFS 有多好 - 创建一个项目，然后尝试将其导出到另一个 TFS 系统 - 据我所知您做不到！
因此，每隔几年，您就必须扔掉所有东西并重新开始 - 因为在 TFS 中，没有内置方法可以导出您所做的所有操作。当您构建新系统时 - 您无法移动所有历史工作项等。您唯一能做的就是手动将代码移动到新系统并重新重新创建所有内容。
这是在您必须移动的每个项目上浪费一周时间的好方法。
If you want to see just how good TFS is - create a project and then try and export it to another TFS system - from what I see you can't!
So every few years you have to throw everythign away and start over again - since in TFS there is no built-in way to export all what you have done. When you build a new system - you cannot move all the history work items etc. only think you can ever do is just move your code MANUALLY to the new system and recreae everything all over again.
Great way to waste a week's worth of work on every project you have to move.