每次打开解决方案时,VSS 绑定都会丢失

发布于 2024-09-25 13:25:05 字数 183 浏览 4 评论 0原文

每次我打开特定的解决方案时,VSS 绑定都会丢失,我必须重新绑定。谁能告诉我为什么会发生这种情况和/或如何防止它(除了永不关闭解决方案,或必须执行“获取最新版本”)?并不是每个项目/解决方案都会发生这种情况,只有这个项目/解决方案才会发生这种情况。

一如既往,感谢您的帮助。

PS我知道这个产品很糟糕,但我必须使用它。

Every time I open a particular solution, the VSS bindings are lost and I have to rebind. Can anyone tell me why this happens and/or how to prevent it (short of never closing the solution, or having to do a "Get Latest Version")? This doesn't happen for every project/solution, only this one.

As always, thanks for the help.

P.S. I know the product sucks, but I have to use it.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

心房的律动 2024-10-02 13:25:05

很难找到问题的根本原因,但它可能与存储在文件夹中的绑定信息的损坏有关。

一种可能的解决方案是删除项目文件夹的内容(您可以先尝试仅删除 VSS 相关文件),然后从源代码管理(在 VS 中)重新打开它,让 VS 重新创建绑定信息。

如果您的团队中只有您正在尝试这个问题,那么这肯定会起作用...否则...不知道。

如果此后问题仍然出现,除了重新安装 VS 之外我没有看到其他解决方案:-(

希望有所帮助!

It's gonna be hard to find the root cause of the problem but it's probably related to corruption of binding informations stored in your folder.

One possible solution would be to delete the content of your project folder (you can try first by only removing VSS related files) and then re-open it from source control (in VS) to let VS recreate binding informations.

This will surely work if only you in your team are experimenting this problem... othewise... don't know.

If the problem still occure after that, I don't see other solution than re-installing your VS :-(

Hope that help !

爱你是孤单的心事 2024-10-02 13:25:05

您使用的是哪个版本的 VSS?

在旧版本的 Visual SourceSafe(6.0c 之前)中,将 Visual Studio 的解决方案添加到其源代码管理后,绑定信息直接存储在 .sln 和 .proj 文件中。

从 VSS 6.0c 开始,所有绑定信息都保存在开发人员计算机上本地名为 MSSCCPRJ.SCC 的文件中。

确定绑定信息的存储位置后,您可以更轻松地查明原因。关闭VS前后,用notebook打开.sln/文件,检查是否包含类似

GlobalSection(SourceCodeControl) = preSolution的 代码
...
结束全局部分

which version of VSS are you using?

In older versions of Visual SourceSafe (before 6.0c), after adding a solution of Visual Studio to its source control, the binding information was stored directly in the .sln and .proj files.

Since VSS 6.0c, all binding information is kept locally in files named MSSCCPRJ.SCC on the developer's machine.

after deciding where the binding info is stored, you can pinpoint the cause easier. before and after closing VS, open the .sln/ file with notebook and check whether it includes code similar to

GlobalSection(SourceCodeControl) = preSolution
...
EndGlobalSection

剩余の解释 2024-10-02 13:25:05

这可能是因为某些东西可能会干扰您计算机上 VSS 解决方案的本地副本。
除了项目文件之外,为您的解决方案设置的本地目录还包含两个附加文件:
一个是 MSSCCPRJ.SCC,另一个是 TheSolutionName.VSSSCC。
在窗口中,它们的图标采用两个指向相反方向的箭头的形式。
我不小心删除了它们(认为它们是垃圾),然后丢失了与 VSS 解决方案的所有绑定。请检查您的机器上是否出现类似情况。

另一个原因可能是 - 在同一台计算机上使用多个版本的 VSS。

It may be because something might be intefering with the local copy of VSS solution on your machine.
The local directory set for your solution contains two additional files besides your project files:
one is MSSCCPRJ.SCC and the other is TheSolutionName.VSSSCC.
In windows, their icons are in the form two arrows pointing in opposite directions.
I had accidentally deleted them (thinking they were junk) and then lost all bindings to the VSS solution. Please check if something similar is happening on your machine.

Another reason could be - using multiple versions of VSS on same machine.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文