"Unspecified error" when trying to open Visual Source Safe from Visual Studio 2003 .NET
-
Did not know where else to post this....I have tried just about everything to get this to work but can't figure out. I am getting "Unspecified error" when trying to open Visual Source Safe from Visual Studio 2003 .NET. I have completely uninstalled VSS and VS.NET the reinstalled, have all updates. I can access VSS and VS.NET by themselves but can't get to VSS from VS.NET when I go to File > Source Control > Microsoft Visual SourceSafe. Anyone have any answers? Thanks, John
-
Did not know where else to post this....I have tried just about everything to get this to work but can't figure out. I am getting "Unspecified error" when trying to open Visual Source Safe from Visual Studio 2003 .NET. I have completely uninstalled VSS and VS.NET the reinstalled, have all updates. I can access VSS and VS.NET by themselves but can't get to VSS from VS.NET when I go to File > Source Control > Microsoft Visual SourceSafe. Anyone have any answers? Thanks, John
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. RESOLUTION 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. Practice sesquipedalianism! ;)