PRB: Visual C++ Integration Does Not Recognize .CLW Files

 Last reviewed: July 2, 1997
Article ID: Q139001
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

SYMPTOMS

In Visual C++ 4.0, you cannot check in or check out the Class Wizard status file (.clw file) for a project that is based on Microsoft Foundation Classes (MFC). The .clw file tracks the mapping between resources and classes for a Visual C++ generated MFC project. The format of this text file is undocumented, but it can be easily regenerated.

STATUS

This behavior is by design.

MORE INFORMATION

When you add a project to source control, Visual C++ does not allow you to include the .clw file under source control. This is because, in a multi- developer environment, it is easier to regenerate a .CLW file. Because the format is undocumented, it would not be easy to merge a .CLW file that results from several developers dynamically adding and removing resources, classes, or OLE information to a project they are working on.

When you check out a project that does not have a .CLW file, Visual C++ detects it and prompts you to recreate it. For a project MDI.MDP in the directory C:\CODE\MDI, you would get a message like this one: 

   The ClassWizard database "C:\code\mdi\MDI.CLW" does not exist.
   Would you like to build it from your source files?
If you answer Yes, Visual C++ scans the AppWizard- or ClassWizard-generated files and rebuilds the .clw file. If the .clw file does not rebuild properly, check the formatting of your file. It may be incorrect. The macros or comments that Visual C++ expects to see to use the file with ClassWizard might be the source of the problem.

With Visual SourceSafe, you can add the .clw file to a project. However, Developer Studio does not allow multiuser merge of this file, so Microsoft recommends that you not put a .clw file under source control.

REFERENCES

For more information on how to regenerate the .clw file, drill down to the "Using ClassWizard" topic in the Visual C++ 4.0 InfoViewer using the following as a guide: 

   Visual C++ Books
      User's Guides
         Visual C++ User's Guide
            Working With Classes
               Working With Classes
                  Using ClassWizard

Keywords : kbinterop kbtool kbtshoot kbusage ssvc vbwin visualc vss
Technology : kbMfc
Version : 4.0 5.0
Platform : WINDOWS
Issue type : kbprb

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: July 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.