BUG: F4 to Go to Error/Tag Doesn't Always Open Source File

Last reviewed: July 31, 1997
Article ID: Q140573

The information in this article applies to:

Microsoft Visual C++, 32-bit Edition, versions 4.0, 4.1, 4.2, 5.0

SYMPTOMS

Some project configurations may cause the Go To Error/Tag functionality in the Developer Studio to fail when you double-click (or press F4) the compile results in the output window.

CAUSE

A subproject or main project that refers to an Include file in a directory outside of the default directory may exhibit this behavior. For example, a workspace with the following directory structure will produce the problem if a compiler error is generated in MyIncludeFile.h. The subproject source files are in the directory .\Subproject.

\toplevel

    .\subproject
    .\include

The .\Include directory contains files that the project source file references with this syntax:

   #include "MyIncludeFile.h"

The build settings for the compiler preprocessor for the project has its Additional Include Directories field set to:

   .\Include

RESOLUTION

Either put the Include files in the .\Subproject directory, or give the complete path name in the compiler preprocessor's Additional Include Directories field:

   <drive>:\toplevel\include

STATUS

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

Keywords          : vcbuglist400 vcbuglist500 VwbIss
Version           : 4.0 4.1 4.2 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: July 31, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.