Visual Studio 2012: Syntax Highlighting is turning off and on

Question

I\'m using VS2012 and I\'m quite happy with it. But the problem is, whem I\'m coding in C++, that the syntax highlighting is turning off an on all over again. Sometimes, the

Answer 1

For me, highlighting always stops working when the first visible line in the editor begins with the characters '//' and I trigger reparsing somehow (CTRL + S for instance).

Highlighting always works fine when the first visible line in the editor begins with anything else, even with a whitespace, and I trigger reparsing somehow.

I could indent all my comments and never experience this problem, but now that I know about it, it's not so annoying anymore, so I let it be.

Answer 2

I know this is a while ago but I have had this same problem appearing randomly until just now.

It would disable when the last line in a file was a single line comment. (// blah blah). As soon as i removed that the text highlighting worked again!

Answer 3

If you're using only Intellisense, you may go to Edit->Intellisense->Toggle Completion Mode (or hit Ctrl + Alt + Space), play with it and see if it works (maybe you've pressed this combination of keys by accident).

I've also installed Update 3 and haven't had any problems since. Who knows..

Answer 4

Edit: In this answer I assume that your problem description is correct. In other words, I'm assuming that occasionally C++ highlighting is working, and the other times the text appears as plain text: completely black and white.

My guess is you are using an extension which modifies or replaces the way Visual Studio highlights C++ code. Try temporarily disabling all of your extensions and checking again if the editor is working. Some extensions might have the Disable button disabled; in that case you'll need to uninstall the extension for this test (possibly through Control Panel → Programs and Features).

As an example of one common extension that completely replaces the C++ highlighter is Visual Assist. However, I do not personally use that product and I haven't heard of any specific problems with it of this nature. I am merely mentioning it as an example of an extension that completely changes the behavior of Visual Studio in regards to syntax highlighting of C++ code.

Answer 5

In my case, it turned out that a large block of code (a 200+ line method) was commented out with // starting in the first column, and this was causing the syntax coloring not to work. I changed the commenting delineation to /* ... */ for that method and all of the syntax coloring was fixed.

Answer 6

Personally, I found that things like:

#if 0// bla-bla

mess up syntax highlighting badly. The solution that works for is to put a space before a comment, like so:

#if 0 // bla-bla