Microsoft KB Archive/317574

= FIX: &quot;Unspecified Error&quot; messages after you rename a subproject in a Visual Studio .NET Enterprise Template project in Visual SourceSafe 6.0c =

Article ID: 317574

Article Last Modified on 8/12/2005

-

APPLIES TO

 Microsoft Visual SourceSafe 6.0C, when used with:  Microsoft Visual Studio .NET 2002 Professional Edition

 Microsoft Visual Studio .NET 2002 Enterprise Architect

 Microsoft Visual Studio .NET 2002 Enterprise Developer 

-

<div class="notice_section">

This article was previously published under Q317574

<div class="symptoms_section">

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 &quot;Unspecified Error&quot; messages.

<div class="cause_section">

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.

<div class="workaround_section">

WORKAROUND
To work around this issue, follow these steps:
 * 1) Close the solution, which may require you to quit the Visual Studio .NET integrated development environment (IDE).
 * 2) Delete all of the .vsscc, the .vssscc, and the .vspscc files from all of the project and solution folders.
 * 3) Reopen the solution.
 * 4) 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.
 * 1) Add the solution to source code control to a new project.

<div class="status_section">

STATUS
Microsoft 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.

<div class="moreinformation_section">

Steps to Reproduce the Behavior
<ol> Follow these steps on computer 1: <ol style="list-style-type: lower-alpha;"> Create a new Visual Basic simple distributed application by using the Enterprise Template projects.</li> Set the Web locations to a web server by using the File Share connection.

To determine which access method you are using, in Visual Studio, click Tools, and then click Options. In the left pane of the dialog box, click Projects, click Web Settings, and then locate the Web Server connection property. The default setting is File share, but you can also select FrontPage Extensions.</li> Add the solution to source code control.</li> Select a Client project, and then check out the project.</li> Press F2 to rename the subproject, type a new name, and then press ENTER.</li> Right-click the Enterprise Template Project, and then click Check Out.</li> When you receive a warning about renaming the project, click Continue.</li> Check in all of the files that are listed in the Pending Checkins dialog box.</li></ol> </li> Follow these steps on computer 2: <ol style="list-style-type: lower-alpha;"> Start the Visual Studio .NET IDE.</li> On the File menu, click Source Control, and then click Open from Source Code Control.</li> Locate the project that you created on computer 1 (step 1c).</li> Open the project to a shared universal naming convention (UNC) path folder.</li> Each time that you receive a &quot;not trusted&quot; warning, click OK.</li> Note the warning that the renamed project is not available, and then click OK.</li> <li>Rename a Web project. Note that the project is renamed, however, the project does not appear as checked out.</li> <li>Check out the Enterprise Template Project file.</li> <li>Rename a client project.</li> <li>Check in the solution.

Notice that you receive multiple recurrent &quot;Unspecified Error&quot; messages.</li></ol> </li></ol>

NOTE: If you rename a file in the .NET IDE, Visual SourceSafe does not rename the corresponding SourceSafe file.

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

305516 INFO: SSAFE: Renames and Deletions Not Supported for Source Code Control Through the Visual Studio .NET IDE

Keywords: kbbug kbfix kbpending kbvs2002sp1sweep KB317574

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.