Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Microsoft Visual Studio IDE Hangs when Modifying File under Microsoft Visual SourceSafe Source Control
| Article ID | : | 949539 |
| Last Review | : | February 21, 2008 |
| Revision | : | 1.2 |
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 Microsoft Visual SourceSafe 6.0 or 2005 as your source code control provider. You try to modify many files or a large file in the Visual Studio 2005 IDE.
Back to the top
Result
The Visual Studio 2005 IDE hangs for an extended period and the message "Updating Pending Checkins..." appears in the status bar. When the message appears, the Visual Studio IDE is not responding.
Back to the top
Cause
The Pending Checkins Window is continuously refreshing and thus tying up resources.
Back to the top
Resolution
| 1. | Three possible steps may alleviated this behavior. Apply them one at a time and test to determine which one fixes the problem.
Make sure that your anti virus software is not scanning the files you place in source control. for more information refer to the following Microsoft Knowledgebase article:
Anti-virus software may impact Visual SourceSafe performance (http://support.microsoft.com/default.aspx?scid=kb;en-us;274051)
|
| 2. | Open Visual Studio 2005, in the main menu choose Tools\Options\Source control\Plug-in settings and uncheck "Perform background status updates."
|
| 3. | Open Regedit and rename the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\ToolWindows\{53544C4D-5C18-11d3-AB71-0050040AE094}
to something else, like __{53544C4D-5C18-11d3-AB71-0050040AE094}.
If you are running a 64-bit operating system, they the key will read:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\8.0\ToolWindows\{53544C4D-5C18-11d3-AB71-0050040AE094}Â and this key needs to be renamed to __{53544C4D-5C18-11d3-AB71-0050040AE094}.
|
       This suppresses the display of the Pending Checkins Window.
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 6.0C |
| • | Microsoft Visual SourceSafe 6.0d |
| • | Microsoft Visual SourceSafe 6.0 Standard Edition |
| • | Microsoft Visual SourceSafe 2005 Standard Edition |
| • | Microsoft Visual Studio 2005 Professional Edition |
| • | Microsoft Visual Studio 2005 Service Pack 1 |
| • | 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 |
Back to the top
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
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please
