问题
Lets say I have this VB.net code in VS2013:
Y = "This is a test of some text."
Z = "And this is another line of text where its longer."
Now I realize I it would be useful to output my loop iterator in Y, so I click in Y and start typing...
Y = "This is a test of some text on "."
Z = "And this is another line of text where its longer."
Now since I don't have a closing quote, VS interprets this as the string (and as you can see from the coloring here in SO, so does the MU parser!)...
Y = "This is a test of some text on " &." Z = "
Which means that Y and Z are "open" strings. Now I complete typing, and VS does this...
Y = "This is a test of some text on " & i & "."
Z = "And this Is another line Of text Where its longer."
Since strings like "is", "where" and "and" are Linq keywords, VS happily "fixes" the camel casing for me. It does this right to the end of the function, which may cause dozens of lines to be fubared.
Please tell me there is an easy way to fix this?
UPDATED: the actual example
来源：https://stackoverflow.com/questions/38084091/vs-vb-keeps-changing-the-capitalization-of-my-strings