BUG: Dependency Information Is Lost After Workspace Is Closed

 Last reviewed: May 12, 1997
Article ID: Q168410
The information in this article applies to:
  • The development environment included with: - Microsoft Visual C++, 32-bit Editions, version 5.0

SYMPTOMS

If there are changes to a header included in a .C file that cause a build to fail and the workspace is closed and re-opened, then the dependency information is lost and the build system will report the build is up-to-date.

CAUSE

The dependency information in the project .IDB file containing the header file was deleted during the failed build.

RESOLUTION

  • Compile the .C file instead of choosing Build from the Build menu.

    -or-

  • Choose Rebuild All from the Build menu.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Note that this only applies to .C files. Files with recognized C++ file extensions (such as .CPP) are unaffected.

Keywords : vcbuglist500 VWBIss kbbuglist
Version : 5.0
Platform : NT WINDOWS
Issue type : kbbug

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