BUG: F4 to Go to Error/Tag Doesn't Always Open Source FileID: Q140573
|
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.
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
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
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.
Additional query words:
Keywords : kbide kbVC kbVC400bug kbVC410bug kbVC420bug kbVC500bug kbVC600bug kbGrpDSTools
Version : winnt:4.0,4.1,4.2,5.0,6.0
Platform : winnt
Issue type : kbbug
Last Reviewed: May 28, 1999