TFS 的源代码控制只是增强的 VSS 还是有显着不同？
我的工作场所正计划迁移到 Team Foundation Server，而且现在还不算太早 - 任何可以远离 Visual SourceSafe 癌症的方法。
但是，我必须问 - TFS 中的源代码管理是否与 VSS 显着不同（并且更好），或者它只是同一事物的“增强”版本？
我现在问这个问题是因为这可能是我最后一次提出类似 Subversion 之类的建议。
My workplace is planning on moving to Team Foundation Server and it's not a moment too soon - anything to get away from the cancer that is Visual SourceSafe.
However, I must ask - is the source control in TFS significantly different (and better) than VSS or is it just a "beefed up" version of the same thing?
I ask this now since this is probably my last window to suggest something like Subversion.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
我们在过去的 18 个月里一直在使用 TFS，并且像许多产品一样，第一个版本还有一些不足之处（TFS 2005 最喜欢的一个就是没有在声称的情况下获得最新版本，从而导致许多构建中断） 。
然而现在我们使用的是 TFS 2008 SP1，它运行得非常好。 源代码控制系统快速、直观，并与 Visual Studio 无缝集成。 对于重命名、移动、分支和合并等操作，它在跟踪事物的能力以及合并分支的能力方面轻松超越了 Subversion 等其他工具。
不管别人怎么说，TFS 源代码管理和 VSS 之间根本没有可比性。 而且您也不必担心您的存储库被损坏！
唯一似乎仍然明显的问题是，每隔几周 TFS 就会变慢，并且获取最新版本需要很长时间，需要重新启动 SQL Server 才能修复。 我不知道这是为什么。
We've been using TFS for the last 18 months, and like many products the first version left a bit to be desired (one of the favourites of TFS 2005 was not to get latest when it said it had, resulting in many build breaks).
However now we're on TFS 2008 SP1 it works exceptionally well. The source control system is fast and intuitive, and integrates seamlessly with Visual Studio. For things like renaming, moving, branching and merging it easily surpasses other tools such as Subversion in terms of how well it tracks things and its ability to merge branches.
In spite of what anybody says, there simply is no comparison between TFS source control and VSS. And you don't have to worry about your repository getting corrupted either!
The only problem that still seems apparent is that every couple of weeks TFS slows down and getting latest takes ages, requiring a restart of the SQL Server to fix. I don't know why this is.
TFS 源代码控制由 SQLServer 提供支持。 我过去使用过 CVS 和 SVN，TFS 源代码管理为我提供了我需要的一切。 请注意，我没有做很多分支，主要是使用发布标签进行直线开发。 我已经与多个开发人员一起使用过它，并且我喜欢合并功能——并排 GUI 允许我选择要应用的冲突版本。 我还没有遇到任何无法解决的问题。 我很高兴我不再寻找其他任何东西。 与 VSS 相比，我更喜欢它。
TFS source control is backended with SQLServer. I've used CVS and SVN in the past and TFS source control provides me with everything I need. Note that I don't do a lot of branching, mainly straight-line development with tags for releases. I have used it with multiple developers and I like the merge features -- side-by-side GUI allowing me to choose which version of conflicts to apply. I haven't run into any insoluble problems yet. I'm happy enough that I'm not looking for anything else. I much prefer it over VSS.
我对 TFS 和 VSS 都有第一手经验。 TFS 和 VSS 之间的唯一共同点是解决方案资源管理器中用于显示文件状态的图标。
TFS 是一个优秀的源代码控制和项目管理解决方案。 它可以支持敏捷实践，并支持 CI 和测试。 它由 SQL 支持，稳健且快速。 如果您想使用 SVNBridge，则可以进行 SVN 样式访问。 它的扩展性非常好，可以应对大型项目。 TFS 团队实际上对此进行了测试并取得了巨大成功。 它的主要缺点是成本和学习曲线。
VSS 可能是我在源代码控制方面见过的最糟糕的尝试，我认为使用旧磁带驱动器上备份的夜间 zip 文件比使用 VSS 更好。
I have first hand experience with both TFS and VSS. About the only commonality between TFS and VSS is the icons used in solution explorer to display file status.
TFS is an excellent source control and project management solution. It can support agile practices and comes with support for CI and testing. Backed by SQL it is robust and fast. You can have SVN style access if you want using SVNBridge. It scales awesomely, and copes with huge projects. The TFS team actually dogfooded this one to great success. Its main downsides are cost, and learning curve.
VSS is probably the worst attempt I've ever seen at source control and I think one would be better off using a nightly zip file backed up on an old tape drive than use VSS.
Sourcesafe 建议用于五人或更少的团队。
TFS 受到 MS 的测试，因为他们将其用于越来越多的项目和成千上万的用户。 有很多细节可以说明为什么它更强大，但这应该说明两者之间的范式步骤。
我从 2006 年初就开始使用 TFS，我发现的所有故障都是 PEBCAK。 它非常可靠。
Sourcesafe is recommended for teams of five or less.
TFS is dogfooded by MS, in that they are using it for an ever increasing number of projects and in the thousands of users. There's lots of details of why it's more robust but this should illustrate the paradigm step between the two.
I've been using TFS since early 2006 and all faults I've discovered are PEBCAK. It is extremely reliable.
对于初学者，您可以让多个人签出相同的文件（但是仍然可以选择专门签出）。
存储是数据库驱动的，而不是文件驱动的。 对我来说，这使得搜索代码库变得更加困难，但它允许更容易的合并和注释（谁写了这行代码？）。
TFS 不仅仅是源代码控制。 任务管理、签入策略，列表还在< /a>
For starters you can have multiple persons have the same file checked out (however there is still the option to exclusively check out as well).
The storage is database driven, instead of file driven. For me this has made searching the codebase harder, but it allows far easier merging and annotations (who wrote this line of code?).
TFS is much more than just source control as well. Task management, check-in policies, the list goes on
我没有使用 TFS 的第一手经验，但我使用过 Source Safe 和 svn。 从我读到的内容来看，你的答案是肯定的，是的。 您绝对可以感受到源代码安全的历史，但同时它是一个现代系统，具有您期望的功能，然后是一些（它也做了很多项目管理的事情）。
I don't have first hand experience with TFS, but I've used both source safe and svn. From what I've read, your answers are yes, and yes. You can definitely feel the source safe history, but at the same time it's a modern system with the features you'd expect and then some (it does a lot of project management stuff too).