Disabling the Spell Check Feature
This question has come up a lot recently. Some people love the integrated spell checking, others hate it. The number one comment we get regarding this feature is the flagging of variable names as spelling errors.
The reasoning here was that variable names should be meaningful words, rather than abbreviations or random letters. This produces more meaningful code that is easier to read. The spell check engine is smart enough to understand camel case, so standard programmer idioms can still be applied. However, realizing that this isn’t for everyone, you do have a couple of options. To configure spell checking, bring up the options panel for Studio Tools from the Visual Studio menu:
Tools | Options
First, you can set Comments Only to true, disabling spell checking inside the code itself.
Alternatively, you can set As-You-Type Spell Checking to false to disable it all together.
You can always execute a manual spell check from the Studio Tools | Spelling menu.
Hopefully this clears up some confusion. We’d love your comments on this feature. For example, should the default state be to only spell check inside of comments? Are there other rules we should teach the engine about that would make the code level spell checking more useful?
| Permalink | Comments[1] |
Recent Entries
» Build 2687 Posted
» New Unit Testing Book
» Build 2293 Update Posted
» Microsoft Team System NUnit Adapter
» MS Team System Test Support
You can leave a response, or trackback from your own site.
July 17th, 2007 at 3:08 pm
One additional feature might be to limit to comments _and_ strings.