Microsoft Knowledge Base Email Alertz

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).

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 318885 - Last Review: August 29, 2005 - Revision: 3.2

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

This article was previously published under Q318885

On This Page

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).

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.

RESOLUTION

To work around this problem, follow these steps:
  1. Follow these steps to disable anonymous browsing on the Web site in question:
    1. Open Microsoft Internet Information Services (IIS).
    2. Right-click the Web site, and then click Properties.
    3. Click the Directory Security tab, and then click Edit in the Anonymous Access and Authentication Control section.
    4. Click to clear the Anonymous Access check box.

      NOTE: If you need anonymous Web browsing, disable write permissions instead.
  2. Log on to the Visual SourceSafe database, and then manually check in the files.
  3. 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.

STATUS

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

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

  1. 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.
  2. Add the solution to source control. This must be the same database that the FrontPage 2000 Server Extensions are pointed to.
  3. On the File menu, point to Source Control, and then click Change Source Control to unbind the solution and the project from source control.
  4. Right-click the project, and then click Properties.
  5. Click Web Settings, and then click to select the FrontPage check box.
  6. Save and close the solution.
  7. Open Microsoft Internet Information Services (IIS), and then follow these steps to add the Web site to source control:
    1. Right-click the Web site, and then click Properties.
    2. Click the Server Extensions tab.
    3. 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.
  8. Open the solution again in the Visual Studio .NET IDE. Notice that you cannot check in the files.

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
    • Microsoft Visual Studio .NET 2003 Enterprise Architect
    • Microsoft Visual Studio .NET 2003 Enterprise Developer
    • Microsoft FrontPage 2000 Server Extensions
Keywords: 
kbvs2002sp1sweep kbbug kbpending KB318885
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate