HOWTO: Use Glyphs in Visual C++ 4.0 with Source Code Control

 Last reviewed: October 10, 1997
Article ID: Q136020
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++, version 4.0

SUMMARY

Visual C++ version 4.0 running under the Microsoft Developer Studio supports integration with a source code control provider, such as Visual SourceSafe. The color and glyphs used in File View reflect the state of any given file within a project workspace relative to Source Code Control.

The information in this article is valid independent of the Source Code Control Provider you use, but is specific to the Microsoft Developer Studio using Visual C++.

MORE INFORMATION

In FileView, if a given file is under source code control, the "file glyph" is gray in color. If the file is not under source code control, it is white in color.

It is possible to create a resource script and check it out, but not check out underlying image files used by the resource script. Developer Studio is smart enough to prompt you to check out, for example, the underlying .bmp file before allowing you to start editing a toolbar bitmap. If you don't check the file out, you won't be able to save any changes you make to the bitmap file.

NOTE: For non-text files, only one user can effectively check the file out at a time.

KBCategory: kbusage kbinterop kbhowto kbtshoot
KBSubcategory: SourceSafe ssvc vss vbwin ssvc visualc
Additional reference words: 4.00 5.00
Keywords : SourceSafe ssvc vbwin visualc vss kbhowto kbinterop kbtshoot 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.