Prevent VB.NET multi-line / verbatim line from destroying your entire code file?

Say you have a module that contains several hundred lines. At the very top of your code file, you run a line, so you enter a quote. The total number of debris occurs because the line remains unchanged for a while, as a result of which everything inside your code file is subject to erroneous encapsulation by your line (see Image for an actual example of all errors created). It's okay, right? You just end your line and all errors disappear. While this is true, you may find that the IDE has its own paths with other lines in your document. For example, these lines ...

oLog.writeLogFile("Starting System Update and Version Update ") oLog.writeLogFile("Starting Script for Fetching Data from Source to Dest") 

... will change to this:

 oLog.writeLogFile("Starting System Update and Version Update ") oLog.writeLogFile("Starting Script for Fetching Data from Source to Dest") 

Notice how the And, To, and To values ​​have changed. What happens here, as other lines in the document become ... eh ... "destrung" ... so some of the words that were once part of the line are now interpreted as IDE keywords. Since he is VB, he automatically changes capitalization. When you finally complete your line, all other lines further down in the document will also complete correctly, but the jarring effects still remain.

Is there any way to prevent this?

enter image description here

+5
source share
1 answer

Why not enter double " , and then go back between them and start typing a line? I do this all the time to prevent this. I find that there is a short delay between entering your first " and the moment the IDE starts using keywords, enough for me (don't forget) to enter the second. "

+1
source

All Articles