You are not Prompted to Edit a file under Source Control when you begin making changes

You are not Prompted to Edit a file under Source Control when you begin making changes

Article ID : 953345
Last Review : May 19, 2008
Revision : 1.1
Source: Microsoft Support

Back to the top

RAPID PUBLISHING

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

Back to the top

Action

You are using Visual SourceSafe 6.0 or 2005.  You attempt to edit a file from within Visual Studio that has not been checked out.

Back to the top

Result

You are able to edit the file without being prompted and without the file being automatically checked out.

Back to the top

Cause

Files in the working directory do not have the read only attribute even though they are not checked out from Visual SourceSafe.

Several scenarios can cause this behavior:

1. You may have selected make writable option when getting files from SourceSafe.

2.  You may not have Tools> Options> Local Files tab  Use Read-only Flag for files not checked out selected.

3. You may be sharing a working directory with another user that does have the file checked out.

4. You may have intentionally uncheck the read only attribute in order to do testing on the file without checking the file out.

5. You may not have NTFS permissions to set the read only in the working directory. 

6. In the dialog Tools> Options> expand Source Control and choose Environment, you set the On Edit option to do nothing and you have checked the box in the same dialogue to Allow checked in items to be edited.

Back to the top

Resolution

Make sure the user has full permissions to their working folder.

In VSS  Explorer:

Open the Tools> Options> Local Files tab and make sure the Use Read-only Flag for files not checked out option has a check mark in it.

or

In Visual Studio:

 Go to Tools> Options> expand Source Control and choose Plug-in Settings.  Click on the advance button and select the Local Files tab and make sure the Use Read-only Flag for files not checked out option has a check mark in it.

In Visual Studio you have the option to be prompted when editing or to automatically check the file out.

In the dialog Tools> Options> expand Source Control and choose Environment.

Set the On Edit option to Prompt for Check out or Automatically check out depending on preference.

Move all the files from the working folder and re-issue the Get Latest (making sure you do not select make writable) and try to edit the file.

Back to the top

More Information

If you do a Get Latest, typically the files should be marked with a read only attribute.  However, sometimes the attribute is not set for some reason. Please review the cause section for most common reasons.

Sharing of working directories is not recommend because it can easily lead to the problem described in this article.

If you are editing directly from the SourceSafe Explorer

Open the Tools> Options> General tab and make sure that the Double-click on a file option is set to Ask.

You are prompted by a dialog that contains the following question in a option group:

Do you want to:

View SourceSafe’s copy of this file

Check out this file and edit it in your working folder.

Back to the top

DISCLAIMER

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Back to the top


APPLIES TO
• Microsoft Visual SourceSafe 2005 Standard Edition
• Microsoft Visual SourceSafe 6.0d
• Microsoft Visual SourceSafe 6.0C
• Microsoft Visual Studio .NET 2003 Professional Edition
• Microsoft Visual Studio .NET 2003 Enterprise Developer
• Microsoft Visual Studio .NET 2003 Enterprise Architect
• Microsoft Visual Studio .NET 2003 Academic Edition
• Microsoft Visual Studio 2005 Professional Edition
• Microsoft Visual Studio 2005 Professional Edition with MSDN Premium Subscription
• Microsoft Visual Studio 2005 Professional Edition with MSDN Professional Subscription
• Microsoft Visual Studio 2005 Standard Edition
• Microsoft Visual Studio 2005 Team Edition for Database Professionals
• Microsoft Visual Studio 2005 Team Edition for Software Architects
• Microsoft Visual Studio 2005 Team Edition for Software Developers
• Microsoft Visual Studio 2005 Team Edition for Software Testers
• Microsoft Visual Studio 2008 Professional Edition
• Microsoft Visual Studio 2008 Standard Edition
• Microsoft Visual Studio Team System 2008 Database Edition
• Microsoft Visual Studio Team System 2008 Architecture Edition
• Microsoft Visual Studio Team System 2008 Development Edition
• Microsoft Visual Studio Team System 2008 Test Edition

Back to the top

Keywords: 
kbnomt kbrapidpub KB953345

Back to the top

 

Microsoft Knowledge Base Article

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


You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

AddThis Social Bookmark Button

Leave a Reply

*
To prove that you're not a bot, enter this code
Anti-Spam Image