CODEWITHSUNDEEP
vb.netvisual-studio
Maury Markowitz
Maury Markowitz

Reputation: 9303

VS keeps changing my camel casing

I have posted on this before, but couldn't find a simple example. Here's one. I had some code commented out. Part if it was a comment. I used un-comment to turn the code back on for testing. And so this...

'check to see if this is a "simple" struct that has only basic types inside, not additional embedded type 5's

Turned into this...

check to see if this Is a "simple" struct that has only basic types inside, Not additional embedded type 5's

Look at the Is and Not. This isn't happening on all keywords, it appears that it's primarily Linq related terms get re-camel cased - Is, On, Where etc. And that's weird, because I don't have or use Linq in any of my projects.

This is annoying, but what is actually damaging is when this happens inside quotes. Let's say you had something like this...

'this is a "really long comment that I want to split into two lines"

Now I place my cursor in front of, say, "I" and hit return. This produces a second line with a trailing quote. Now every keyword in the entire file from that point on is re-cased, because there's an open quote confusing VS. Now my git diff is basically screwed.

Does anyone have any suggestions on what might be happening and how to turn it off?

Upvotes: 0

Views: 116

Answers (1)

TnTinMn
TnTinMn

Reputation: 11801

The re-casing of keywords is a feature of "Pretty listing (reformatting) of code". This feature was less aggressive in VS versions earlier then VS2015 and did not run un-commenting a line.

To disable it go to:

Tools Menu->Options->Text Editor->Basic-> Advanced-> Editor help section

and uncheck "Pretty listing (reformatting) of code".

Upvotes: 3

Related Questions