HOWTO: Move or Rename Files Used with Visual C++

 Last reviewed: October 10, 1997
Article ID: Q136021
4.00 5.00 | 4.00 5.00 
WINDOWS   | WINDOWS NT
kbusage kbinterop kbhowto

The information in this article applies to:

  • Microsoft Visual SourceSafe for Windows, versions 4.0, 5.0
  • Microsoft Visual SourceSafe for Windows NT, versions 4.0, 5.0
  • Microsoft Visual SourceSafe for Windows 95, versions 4.0, 5.0
  • Microsoft Visual C++, 32-bit Edition, version 4.0

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.

REFERENCES

For additional information on how glyphs are used to represent that state of a project under source code control within the Visual C++ Developer Studio, please see the following article in the Microsoft Knowledge Base: 

   ARTICLE-ID: Q136020
   TITLE     : How to Use Glyphs in Visual C++ 4.0 with Source Code Control

KBCategory: kbusage kbinterop kbhowto
KBSubcategory: SourceSafe ssvc vbwin visualc
Additional reference words: 4.00 5.00
Keywords : SourceSafe ssvc vbwin visualc kbhowto kbinterop kbusage
Version : 4.00 5.00 | 4.00 5.00
Platform : NT WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: October 10, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.