Microsoft KB Archive/136021

= How To Move or Rename Files Used with Visual C++ =

Article ID: 136021

Article Last Modified on 7/1/2004

-

APPLIES TO


 * Microsoft Visual SourceSafe 4.0 Standard Edition
 * Microsoft Visual SourceSafe 5.0 Standard Edition
 * Microsoft Visual C++ 4.0 Standard Edition

-



This article was previously published under Q136021



SUMMARY
Visual C++ is tightly coupled with the Source Code Control Provider, such as Visual SourceSafe. This tight integration means that changes made within Visual SourceSafe explorer will be reflected immediately within the Visual C++ Developer Studio.



MORE INFORMATION
The Visual C++ Developer Studio uses glyphs and different colored icons to represent the status of any given file within Source Code Control. Specifically, if a given file within FileView is under Source Code Control, that file's icon is gray in color. If it is not under source code control, it is white in color.

You can add files to a project under source code control. On the Tools menu, click Source Control and then click Add To Source Control. You can also remove files from source code control. On the Tools menu, click Source Control, and then click Remove From Source Control.

Within the Visual SourceSafe Explorer, you can rename a file or a project that the file is in. If you do so while the Visual C++ Developer Studio is running, the glyphs will probably change to reflect the new state of either the file or project.

If you just moved or renamed a single file or subset of files within a project workspace, the checkmark glyphs, if present, for those files will disappear, and the file icon will shift from gray (under source code control) to white (not under source code control). If you moved or renamed the entire project, all glyphs will change to indicate this.

If you restore the original file name or move it back to its original location within the Visual SourceSafe Explorer project tree, Visual C++ will detect this and restore the glyphs as necessary to reflect the current state of that file.

This tight coupling allows Visual C++ and a source code control provider to work together seamlessly.

