Microsoft KB Archive/318885

= FIX: You cannot check a project after you change your Web access method from &quot;File Share&quot; to &quot;Front Page&quot; in Visual SourceSafe 6.0c =

Article ID: 318885

Article Last Modified on 8/29/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

 Microsoft Visual Studio .NET 2003 Professional Edition</li></ul>

 Microsoft Visual Studio .NET 2003 Enterprise Architect</li></ul>

 Microsoft Visual Studio .NET 2003 Enterprise Developer</li></ul>

 Microsoft FrontPage 2000 Server Extensions</li></ul> </li></ul>

-

<div class="notice_section">

This article was previously published under Q318885

<div class="symptoms_section">

SYMPTOMS
After you change your Web access method from File Share to Front Page, you cannot check in the project from the Visual Studio .NET integrated development environment (IDE).

<div class="cause_section">

CAUSE
This problem occurs because of a bug in FrontPage 2000 Server Extensions that does not forward your domain information correctly to the Visual SourceSafe database.

<div class="resolution_section">

RESOLUTION
To work around this problem, follow these steps: <ol> Follow these steps to disable anonymous browsing on the Web site in question: <ol style="list-style-type: lower-alpha;"> Open Microsoft Internet Information Services (IIS).</li> Right-click the Web site, and then click Properties.</li> Click the Directory Security tab, and then click Edit in the Anonymous Access and Authentication Control section.</li> Click to clear the Anonymous Access check box.

NOTE: If you need anonymous Web browsing, disable write permissions instead.</li></ol> </li> Log on to the Visual SourceSafe database, and then manually check in the files.</li> On the Project menu in the Visual Studio .NET IDE, click Web Project, and then click Recalculate Links. Notice that the files show that they are checked in.</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

<div class="moreinformation_section">

MORE INFORMATION
When FrontPage 2000 Server Extensions check out the file to write the connection information, FrontPage 2000 Server Extensions drops the domain information from your user ID. Therefore, although the project shows that it is checked out by User, the conflict occurs because the IDE properly uses Domain\User when you try to check in the project.

Steps to Reproduce the Behavior
<ol> Create a Microsoft ASP.NET Web application in Microsoft Visual Basic .NET. Make sure that you use File Share access for the Web access method.</li> Add the solution to source control. This must be the same database that the FrontPage 2000 Server Extensions are pointed to.</li> On the File menu, point to Source Control, and then click Change Source Control to unbind the solution and the project from source control.</li> <li>Right-click the project, and then click Properties.</li> <li>Click Web Settings, and then click to select the FrontPage check box.</li> <li>Save and close the solution.</li> <li>Open Microsoft Internet Information Services (IIS), and then follow these steps to add the Web site to source control: <ol style="list-style-type: lower-alpha;"> <li>Right-click the Web site, and then click Properties.</li> <li>Click the Server Extensions tab.</li> <li>Click Use External from the drop-down list box, and then add the project to the same location that you added the project to in step 2.</li></ol> </li> <li>Open the solution again in the Visual Studio .NET IDE. Notice that you cannot check in the files.</li></ol>

Additional query words: checkin checkout

Keywords: kbvs2002sp1sweep kbbug kbpending KB318885

-

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

© Microsoft Corporation. All rights reserved.