Reputation: 49
have been using Visual Studio Express 2010 (C++) well and fine for a good while now, but all of a sudden the error highlighting seems to have turned itself off when editing any file other than main.cpp
I've checked my settings and as far as I can tell they're fine - everything enabled in IntellSence etc. Have restarted my machine a couple of times Have completely re-installed VS. Have checked it in another project so I don't think it's a prject specific problem.
This seems pretty weird to me. Does anone have any idea what might be going on?
Cheers.
Upvotes: 4
Views: 7628
Reputation: 11
I had 2 projects in one solution and the intellisence only worked in one project. The intellisence started working only after i commented a specific line in of code in my project. it was a complex get function.
Upvotes: 0
Reputation: 314
Try removing this file that may have been accidentally added in c/c++ code:
#include< dbdao.h >
hope this helps !
Upvotes: 0
Reputation: 136
I had the same problem and none of the answer posted here helped me.
if your project is under some source control (mine was under ClearCase), this solution might work for you.
You need to make sure that .sln , .suo and .vcxproj.user are editable.
Intellisense need these files to be editable else it will not work.
Hope this helps someone.
Upvotes: 1
Reputation: 1
Tools->Options->Text Editor->c/c++->General-> uncheck "Word wrap" (under settings) Could solve the problem. Thanks
Upvotes: 0
Reputation: 11
Upvotes: 1
Reputation: 1
I had an issue where the error highlighting occurred in VS2010 out of the blue on a header file, but which the project compiled and built fine. I did the Project->Rescan and all of the erroneous error hightlights (code with underlined red) disappeared.
Upvotes: 0
Reputation: 1852
Sometimes this just happens, I assume because of some code that the Intellisense compiler chokes on. A trip to Project > Rescan Solution will fix it, at least until the next time...
Upvotes: 0
Reputation: 23876
Go to Options -> Text Editor -> C/C++ -> Advanced, and check "Underline errors in the editor" and "Show live semantic errors".
Upvotes: 2