FIX: "Unspecified Error" messages after you rename a subproject in a Visual Studio .NET Enterprise Template project in Visual SourceSafe 6.0c (317574)
The information in this article applies to:
- Microsoft Visual SourceSafe 6.0c, when used with:
- Microsoft Visual Studio .NET (2002), Professional Edition
- Microsoft Visual Studio .NET (2002), Enterprise Architect Edition
- Microsoft Visual Studio .NET (2002), Enterprise Developer Edition
This article was previously published under Q317574 SYMPTOMS
If you rename a subproject in a Visual Studio .NET Enterprise Template project before you check out the solution, Visual SourceSafe updates the solution but does not check out the solution.
Later, when another user tries to work with the source code control copy of the project, the user may receive "Unspecified Error" messages.
CAUSE
When you rename the subproject, Visual SourceSafe updates the source control information in memory to the solution file. However, because you did not check out the solution file, SourceSafe does not change the source control copy of the solution.
WORKAROUND
To work around this issue, follow these steps:
- Close the solution, which may require you to quit the Visual Studio .NET integrated development environment (IDE).
- Delete all of the .vsscc, the .vssscc, and the .vspscc files from all of the project and solution folders.
- Reopen the solution.
- Remove any projects that will not load, and then add them.
Projects may not load for several reasons, for example, because the binding information may be incorrect, or because you may receive errors. - Add the solution to source code control to a new project.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This bug was corrected in Visual Studio .NET 2003.
Modification Type: | Minor | Last Reviewed: | 8/12/2005 |
---|
Keywords: | kbvs2002sp1sweep kbfix kbbug kbpending KB317574 kbAudDeveloper |
---|
|