您对 Visual SourceSafe 有什么看法？
我正在考虑购买 VSS，想知道人们对此有何具体想法？
I am considering getting VSS and was wondering what were people's thoughts on it in particular?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
众所周知，它会损坏数据。有很多更好的选择。如果您需要匹配功能集和 GUI，请查看 SourceGear 的 Vault。免费的替代品有很多——从无处不在的 svn 到更现代的（分布式）git、mercurial 等。
此外，TFS 是 MS 的替代品——如果您想要 MS 工具，至少使用 TFS。
It's well-known to corrupt data. There are many better alternatives. If you need to match the feature-set and GUI, check out Vault from SourceGear. Free alternatives are numerous --- from the ubiquitous svn to the more modern (distributed) git, mercurial, etc.
Also, TFS is the MS replacement -- if you want MS tools, at least use TFS.
Jeff Atwood 有一篇不错的文章： 除 SourceSafe 之外的任何内容
当有其他解决方案时，没有理由使用 VSS，例如 SVN、Git 和 Mercurial 与 VSS 相比，它在可靠性方面更好，并且使用更现代的方法。
Jeff Atwood has a nice post: Anything But SourceSafe
There is no excuse for using VSS when there are other solutions such as SVN, Git and Mercurial which are better both in terms of reliability and use more modern approach then VSS.
我的想法：
啊哈哈哈哈哈哈哈哈哈哈HRHRHRHGGEHAGTJH@#$@!&#&$!&@#@!@#%^@#$%
不，说真的。
在我知道它有多邪恶之前（新手开发者），我使用了它。然后，它破坏了我正在从事的整个项目。真是一堆垃圾。
使用 Subversion、Git 或 Mercurial...为了您自己的理智。
My thoughts:
AHHHHHHHHHRHRHRHGGGEHAGTJH@#$@!&#&$!&@#@!@#%^@#$%
No. Seriously.
Before I knew how evil it was (newbie dev), I used it. Then, it corrupted an entire project I was working on. What a pile of garbage.
Use Subversion, Git, or Mercurial...for your own sanity.
Microsoft 正在推动 Team Foundation Server (TFS) 作为 VSS 的替代品。 VSS 确实提供了基于文件的系统的简单性，但您将经常花费大量时间修复数据库。 TFS 是一个更加可靠的基于服务器的系统。 Visual Studio 2010 附带 TFS 的客户端许可证和最多 5 人的服务器许可证。你最好把钱放在那里。
TFS 成本。
由于问题是许可证/价格问题，您可以在周一至周五上午 6:00 至下午 6:00（太平洋时间）致电 1-800-426-9400，直接与 Microsoft 许可专家交谈，您可以从那里获取更多详细信息。
Microsoft is pushing Team Foundation Server (TFS) as a replacement for VSS. VSS does offer the simplicity of a file based system, but you will spend a good amount of time repairing the database every so often. TFS is a much more reliable server based system. Visual Studio 2010 comes with a client license and a up to 5 person server license of TFS. You are better off putting your money there.
TFS Costs.
Because the question is a license/price issue, you can call 1-800-426-9400, Monday through Friday, 6:00 A.M. to 6:00 P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist, and you can get more detail information from there.
使用 TFS、Perforce 或 git。
即使 SourceSafe 使用起来并不是极其危险（腐败，已经提到过）……仅仅拥有用于源代码控制的文件版本确实很糟糕。令人难以置信的是，这种类型的源代码控制仍然被广泛使用。
您需要变更集或基于任务的源代码控制。您将希望轻松了解哪些文件发生了特定更改……而不仅仅是一堆独立递增的文件编号。
Perforce 非常快，我对此非常满意。
我为一个主要客户使用 TFS，效果也相当不错。在我设置 Perforce 时，TFS 需要一个服务器操作系统和某个地方的许可证。我不想再设置一个虚拟机，所以我选择了 Perforce。
不过，今天我仍然会轻松选择 Perforce。这主要是因为我使用多个平台。由于主要的 Perforce GUI 客户端使用 Qt，因此它在任何操作系统上的外观和工作方式都相同。
Use TFS, Perforce, or maybe git.
Even if SourceSafe wasn't extremely dangerous to use (corruption, mentioned already)... just having file versions for source control really sucks. It's almost unbelievable that this type of source control is still widely used.
You want changeset or task-based source control. You'll want to easily know what files went into a specific change... not just a bunch of independently incrementing file numbers.
Perforce is VERY fast, and I'm very happy with it.
I use TFS for one major client, and it's been pretty good too. At the time I set up Perforce, TFS required a Server OS and license for that somewhere. I didn't want to have to set up yet another VM, so I went with Perforce.
I'd still easily choose Perforce today, though. That's mostly because I work with multiple platforms. As the main Perforce GUI client uses Qt, it looks and works the same on any OS.
对于某些情况，VSS 可能是正确的答案（例如：使用 Visual Studio 的一小群开发人员，通常不进行并发开发、容错环境（备份）等）。我认为更重要的问题是你的版本控制如何适应你的整体开发和开发。发布过程。 VSS 和 git 在一些非常重要的方面在概念上是非常不同的，SDLC 的工作方式是选择控制系统的一个重要方面。
VSS might be the right answer for some situations (e.g.: small group of devs using visual studio, not generally doing concurrent dev, fault tolerant env. (back-ups), etc.). I think the more important question is how your version control fits into your overall dev & release process. VSS and git are conceptually very different things in some very important ways and how your SDLC works is an important aspect of choosing a control system.