

V2.12 - Messed up the version numbers back with 2.11, now VS users aren't seeing updates when they check from the VS extension manager. V2.13 - Fixed an occasional issue where the extension would fail to load in such a way that could crash VS or at least block the editor from loading, due to the definition assembly not being found by VS when loading the extension.
WORD 2016 CRASHES WHEN OPENING SPELL CHECK WINDOWS
Spell checking should no longer happen in certain non-editable editor instances in tool windows Words that look like filenames are skipped, as well as words that contain digitsģ.
WORD 2016 CRASHES WHEN OPENING SPELL CHECK CODE
Code nuggets in ASPX files are no longer spell checked as if they were just plain textĢ. * Make sure spell checking is correctly enabled/disabled when you add or remove multi-line comments.ġ.

* Fix a recently introduced bug where adding a word to the dictionary or ignore list in one file wouldn't affect other open files * Fairly significant perf improvements that would affect typing and CPU usage of the background spell checking thread This may change in the future, as it may end up ignoring certain documents that we don't want to ignore. not code definition window or refactor preview window). * Only show spelling suggestions on Primary Documents (e.g. This has a practical benefit (less pieces of words will be ignored, especially with the new logic around ignore words with numerals, underscores, and period) and possibly a performance benefit (in that fewer words may get spell checked). * Be smarter about splitting up words and avoiding punctuation. * Removed the tooltip that appears when you hover over spelling errors (it was just showing the word that was misspelled, again, so it wasn't useful). * You can now change the color of the spelling error squiggle by changing the Spelling Error item in Tools->Options->Environment->Fonts and Colors If you are still seeing crashes, please report them in the Discussions tab. V2.18 - Fix crashes on close file/solution/VS. V2.20 - Avoid a couple more possible crashes from background work. This causes a misspelling like "Hitchiker's" to be marked with only "Hitchiker" as misspelled, offer "Hitchhiker's" as a correction, and become "Hitchhiker's's" when it is inserted. Also work around a possible bug in WPF's spell checking logic where words that end in "'s" don't have those characters included in the error span, but do include those as part of the suggestions. V2.21 - Don't spell check URLs or XML doc tags. Thanks to Michael Lehenbauer for contributing the fix! V2.22 - Major perf update - Fixes the perf issue with large C# files, which would peg the CPU at 100% and never let up. V2.23 - Fixes crash that would happen if the spell checker ran enough times (~15,000), due to window handle exhaustion from not explicitly shutting down a Dispatcher on the background spell check thread. V2.25- Installable on VS2013 (now that the vsgallery has unblocked this extension) You can configure the color of the squiggle under misspelled words by changing the foreground color of Spelling Error (in Tools->Options->Environment->Fonts and Colors).

This extension provides spell checking support for various "natural language" portions of files.
