Article ID: 206665 - View products that this article applies to.
This article was previously published under Q206665
This article has been archived. It is offered "as is" and will no longer be updated.
The following problem can occur when multiple developers are working with a Visual C++ workspace, under Source Control, containing multiple projects.
The Get Latest Version command from the Visual SourceSafe menu doesn't refresh all the projects in the workspace even though their settings have changed.
The solution is to close the workspace and re-open it after doing the Get Latest Version.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
This bug was corrected in Visual Studio 6.0 Service Pack 3.
For more information about Visual Studio service packs, please see the following articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/194022/EN-US/ )INFO: Visual Studio 6.0 Service Packs, What, Where, Why
(http://support.microsoft.com/kb/194295/EN-US/ )HOWTO: Tell That Visual Studio 6.0 Service Packs Are Installed
When one user changes the project settings on multiple projects and other users have this workspace open already, they can issue a Get Latest Version from the Visual SourceSafe menu and refresh all the local files on their system. Not all the projects may be reloaded, and they will not have the changes reflected in the IDE.
Closing and re-opening the project will reload all the information from the files for each project.
Steps to Reproduce Behavior
Article ID: 206665 - Last Review: February 21, 2014 - Revision: 1.0