与其他版本相比，Visual Studio Team Foundation Server 的主要优点是什么？
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
接受 或继续使用网站，即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论（4）
您已经掌握了 TFS 的许多出色功能（持续集成、团队构建、单元测试集成）。我参与过的团队的其他一些功能包括：
You have a lot of the great features of TFS nailed already (continuous integration, team builds, unit test integration). Some of the other features the teams I've been on have included:
根据我个人使用 SourceSafe 的经验，我想 TFS 也会有同样的问题，如果你有任何远程开发人员使用服务器上的默认语言以外的语言，你会一直头痛。恕我直言，外包连接的能力也很糟糕。我迁移到了 SVN，一个不错的错误跟踪系统，并实施了一些测试策略，并且没有回头。另外，它的价格也便宜很多……
In my personal experience with SourceSafe, and I'd imagine that TFS will have the same issues, if you have any remote developers with the default languages other than the one on the server, you'll have constant headaches. IMHO, the ability to outsource connectivity stinks as well. I migrated to SVN, a decent bug tracking system, and implemented some testing policies, and haven't looked back. Plus, it's a heck of a lot cheaper...
从流程角度来看，它为您的 TFS 项目提供了以下两个模板可供选择
除了上述模板之外，Scrum 模板还可从 Scrum 团队系统
From a process perspective, it comes with the following two templates to choose from for your TFS project
In addition to above templates, Scrum template is available from Scrum for Team System
我曾参与过一个大型 BizTalk 2006 项目，以及使用 Subversion/TeamCity（构建服务器）和 Tortoise 的个人 BizTalk 项目，这些项目都运行得非常好；我现在正在开发一个基于TFS2010的小型BizTalk 2009项目，这很痛苦。
这可能只是我（缺乏）使用 TFS 的经验，但它看起来并不“完美”；考虑到我需要在 Visual Studio 中完成所有操作，我感觉好像我正在失去对 VS 中不易放置的许多工件的控制（是的，我知道 2009 现在是一等公民）。
如果我要决定要关闭哪个平台，我会使用 Subversion/TeamCity 和 Tortoise（或者可能是 Mercurial，但我还没有时间对此进行调查）。从成本角度来看，对于小型项目，认为“零”。在功能方面，它们实现了 TFS 可以做的一切 - 分支、合并、持续集成等。事实上，我刚刚向一个拥有小型 BizTalk 开发团队、希望从 Sourcesafe 迁移的客户提出了这个建议。
I've worked on a large BizTalk 2006 project, and personal BizTalk projects using Subversion/TeamCity (build server) and Tortoise which all worked extremely well; I'm now working on a small BizTalk 2009 project based on TFS2010 and it is painful.
It could simply be my (lack of) experience with TFS, however it doesn't seem 'polished'; and given the fact that I need to do everything in Visual Studio, I feel as though I am losing control over many artifacts that do not easily sit within VS (yes I know that 2009 is now a 1st class citizen).
If I were making the decision as to which platform to go down, I would use Subversion/TeamCity and Tortoise (or possibly Mercurial but I haven't had time to investigate that yet). From a cost perspective, think 'nil' for a small scale project. In terms of features, they achieve everything that TFS can do - branching, merging, continuous integration etc. In fact, I've just made this recommendation to a client with a small BizTalk development team who are looking to move from Sourcesafe.