如何修复 Visual Sourcesafe 中的目录结构？
我将 Visual SourceSafe 与 Visual Studio 结合使用。 每当我在一个项目上工作一段时间时，我的硬盘上的目录结构就会变得混乱。 文件的最新版本将转到它们自己的嵌套文件夹，因此我最终得到 C:\VS2005\Projects\MyProject\MyProject\MyProject\MyProject
是什么原因造成的？
I use Visual SourceSafe with Visual Studio. Every time I work on a project for a while, the directory structure on my harddisk gets messed up.
The latest versions of the files are going to their own nested folder, so I end up with C:\VS2005\Projects\MyProject\MyProject\MyProject\MyProject
What is causing this?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
我无法帮助解决您的特定问题，但我记得几年前我自己使用 SourceSafe 时所经历的痛苦。
如果您可以选择使用的源代码控制系统，我建议您看看其他选项。 有几个不错的可供选择。
我切换到 SVN 并且再也没有回头。 它比 SourceSafe 好光年，如果您使用 visualsvn 服务器 (免费产品）。 至于 Visual Studio 集成，visualsvn 客户端大约是 50 美元，或者直接使用 ANKH + 乌龟（两者都是开源的并且非常好）。 最重要的是，交换机不需要花费任何金钱，并且安装程序包可以快速让系统在客户端和服务器上运行。
希望这对您有所帮助，如果您必须继续使用 SourceSafe，祝您好运。
更新：另请参阅此线程
I can't help with your particular problem, but I remember my own pains using SourceSafe just a few years ago.
If you have a choice on the source control system you use, I'd recommend taking a look at other options. There are several good ones to choose from.
I switched to SVN and never looked back. It is light-years better than SourceSafe and setup only takes a few minutes if you use visualsvn server (a free product). As for Visual Studio integration, visualsvn client is about $50, or just use ANKH + Tortoise (both are open source and very good). Bottom line is that the switch doesn't have to cost any money, and the installer packages are quick to get the system running on both the clients and the server.
Hope that helps, and good luck with SourceSafe if you have to keep using it.
Update: See also, this thread
你将需要一个老牧师和一个年轻牧师......或者一个更好的版本控制系统。
You're going to need to get an old priest and a young priest... or a better version control system.
是什么原因造成的？
恐怕只是 VSS 和 VS 结合起来的一般反预期疯狂。 您可以花时间真正了解 VSS 以及它如何看待事物以及如何避免怪癖和陷阱，但它是一个过时的野兽，我支持罗伯特的断言，即给自己买一份副本更有利可图SVN 和 VisualSVN 再也不用担心这个问题了。
What is causing this?
Just the general contra-expectation insanity which is VSS and VS combined I'm afraid. You could spend the time to really get to know VSS and how it thinks of things and how to avoid the quirks and pitfalls, but the thing is such an outdated beast I'd second Robert's asssertion that it's more profitable to get yourself a copy of SVN and VisualSVN and never worry about this again.
我不禁同意其他先生的观点，尽快逃离VSS。 如果你还没有被它咬过，你一定会的。 任何工具都会更好，无论是 Subversion、Mercurial 还是其他工具。 前两个具有名为 Tortoise{SVN,HG} 的扩展，如果您不喜欢 CLI 工具，它将使您能够使用用户友好的界面。 我自己的选择是 HG（也称为 Mercurial），因为它是一个去中心化/分布式 VCS，可以离线使用工作/提交和更轻松的分布式工作。
I can not help but be in agreement with the other gentlemen, run away from VSS as fast as you can. If you have not been bitten by it already, you will. Any tool will be better, be it Subversion, Mercurial or others. The fist two have extensions named Tortoise{SVN,HG} that will enable you to play with a user-friendly interface if you don't like CLI tools. My own choice is HG (also known as Mercurial) as it is a decentralized/distributed VCS which enable offline work/commits and easier distributed work.