> intellisense randomly breaking and putting a red line underneath half your statements

There's a reasonably simple solution with which you can solve the red line problem, if you're talking about the C and C++ projects:

http://connect.microsoft.com/VisualStudio/feedback/details/5...

"Posted by JoeWoodbury on 25/02/2010 at 10:16 (...)

The solution is to add the location of the stdafx.h file to the include path list. This is often a matter of simply putting a dot comma (.,) as the very first item in a projects include list."

It happens regardless of precompiled headers, so I don't think that's the issue. I do think it's an include problem, but I don't know why.

It's precompiled headers and it can be proved: If you would try to turn off precompiled headers in your project and rebuild it, the compilation would fail in all the files in which you see the red lines. It's because your project has subfolders and the files in the subfolders reach stdafx only by accident of having the "use precompiled headers" turned on. So once you fix the include path, and that you can do on the project level, your project will compile independently of "use precompiled headers" settings and the intellisense would work too. I know from experience, I fixed the big projects on which I worked.

EDIT v2: Looking at the project you cited in the reply of this message and the file: http://code.google.com/p/freetype-gl/source/browse/trunk/dem... on the computer on which I don't have VS, I still have an idea what the reason for such errors are: the project authors use something like:

     #elif defined(_WIN32) || defined(_WIN64)

Now think about it: when intellisense parses the file, can it assume you're building a 32-bit version? No. Can it assume you're building a 64-bit version? No. So intellisense doesn't use the header inside that elif at all. Setting defines in the project can fix that.

I'm not using PCH in the most recent example. I've been playing with this project: http://code.google.com/p/freetype-gl/ , so it includes Freetype, GLUT (using freeglut), and opengl stuff. Builds fine, intellisense lines everywhere.

That's actually not it, but that idea helped me to find the issue. L52-56, this Freetype preprocessor magic defeats Intellisense https://code.google.com/p/freetype-gl/source/browse/trunk/te...

I feel silly for never mousing over the three characters at line 62 where Intellisense describes the problem it's having.

>It's definitely nowhere near as annoying as intellisense randomly breaking and putting a red line underneath half your statements.

I feel your paIEnumerable