Visual Studio 2008“文件另存为”对话框间歇性问题
我和我的一些同事在 Visual Studio 2008 和 Windows 7（64 位）中遇到了一个奇怪的问题。我们使用 VSS6 进行源代码控制（不幸的是）。
我们遇到一个问题，我们将对签出的文件进行更改，导致文件按预期签出。但是当我们去构建项目，或者尝试保存文件时，它经常（但并非总是）提示我们“文件另存为”对话框，就好像 VS 认为该文件已签入（因此具有只读标志设置）。
然而，我们所要做的就是取消对话框并再次保存或构建，第二次总是会起作用，而不会提示另存为对话框。或者，我们可以进行另存为，保持名称不变，这样就可以了。就好像 VS2008 中的源代码管理状态没有跟上 VSS（即使我们 VS2008 是签出文件的应用程序）。
这类似于此线程的讨论，但这不是权限或以管理员身份运行的问题，1）因为它在第二次尝试时自行解决，2）我们已经以管理员身份运行 VS。
提前致谢。
杰拉德
Me and a few of my coworkers are experiencing an odd issue in Visual Studio 2008 and Windows 7 (64-bit). We use VSS6 for our source control (unfortunately).
We have an issue where we will make a change to a checked-out file, resulting in the file getting checked out as expected. But when we go to build the project, or try to save the file, it will often (but not always) prompt us with the "Save File As" dialog, as if VS thinks the file is checked-in (and thus has the read-only flag set).
However, all we have to do is cancel out of the dialog and save or build again, and it will always work the second time, without prompting the save as dialog. Or, we can go through with the save as, leaving the name the same, and it will work. It's as if the source control status in VS2008 hasn't caught up w/ VSS (even though we VS2008 was the app that checked the file out).
This is similar to the discussion on this thread, but it's not an issue of permissions or running as administrator, 1) because it resolves itself on second attempt, and 2) we're already running VS as administrator.
Thanks in advance.
Jerad
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我在 Windows 7 和 SCM（甚至使用 SVN）下遇到的麻烦之一是自动索引功能。确保您已将包含源代码的文件夹关闭。我没有任何证据表明它会给 VSS 带来问题，但它看起来就像 VSS 一样脆弱，打开它几乎肯定会出现问题。
顺便说一句，您确实知道在使用 VSS 的公司工作会被终身禁止使用 StackOverflow，对吧？
One thing I had trouble with under Windows 7 and SCM (even with SVN) was the auto-indexing feature. Make sure you have it turned off for the folders that contain your source code. I don't have any evidence it causes problems for VSS but it seems like as fragile as VSS is, having it turned on will almost certainly be problematic.
BTW, you do know that working for a company that uses VSS, is grounds for being barred from StackOverflow for life, right?