KB953345: You are not Prompted to Edit a file under Source Control when you begin making changes
KNOWLEDGE BASE SOLUTIONS
KNOWLEDGE BASE SOLUTIONS 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.Link to Original Article from Microsoft Support
You are not Prompted to Edit a file under Source Control when you begin making changesAction
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.
Result
You are able to edit the file without being prompted and without the file being automatically checked out.
- Edited byXiaoyun Li – MSFT Thursday, August 28, 2008 4:10 AMedit
- Edited byXiaoyun Li – MSFT Wednesday, September 03, 2008 6:17 AMedit
- Edited byXiaoyun Li – MSFT Thursday, September 04, 2008 2:26 AMedit
- Edited byXiaoyun Li – MSFT Tuesday, September 16, 2008 10:11 AMedit
Answers
- 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".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.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.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.- Marked As Answer byXiaoyun Li – MSFT Thursday, August 28, 2008 4:12 AM
All Replies
- 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".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.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.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.- Marked As Answer byXiaoyun Li – MSFT Thursday, August 28, 2008 4:12 AM


