# Spell Checker

Free

## An editor extension that checks the spelling of comments, strings, and plaintext as you type.

(102)
Visual Studio
2015, 2013, 2012, 2010
(240,011)
11/9/2015
2.26
View
Description
Reviews (102)
Q and A (85)
Sort by:

| Thu 3:42 AM

It's really good! However, now that I'm on windows 10, it causes
Visual Studio 2012, 2013 and 2015 to crash when editing C/C++
applications often. When the spell check is uninstalled, VS
does not crash.

Please fix this! It's really awesome. I want it to work.

| January 14 2016

This keeps causing my VS 2015 to crash when I open files that have ALOT of errors(the errors are mainly caused by the spell check trying to check fields that arn't really words..)

by jerryol | January 07 2016

| December 21 2015

"needs to be included with VS" ... I 101% agree!

Thanks guys for sharing that good work!

One suggestion: can you add some C# language words to the "correct words list"?

Example: in Italian, commented code have "bool", "if", "this", etc. marked as errors.

I understood that when you worked with English langue active all worked fine ;)

Thanks.

| November 16 2015

needs to be included with VS

| August 18 2015

I love this plugin it has helped me a lot!
Keep up the good work.

| August 13 2015

using windows 8.1. Can't get it to work...unclear

by bdszuter | July 13 2015

Works very well for our C++ projects in VS2012. So far I've been impressed with how it has handled rather large (20K LOC) files without any obvious performance penalty.
This extension has been especially useful for editing pages of Doxygen documentation.

by TMOII | April 23 2015

| April 02 2015

By default, it underlined almost EVERY WORD in comments on my machine, because it was trying to check the spelling in French, and the comments were in English. There is no option to change the language. Fortunately I thought of switching the language in the taskbar, which works, but it is far from obvious, and has the undesirable effect of changing the language for all apps, not just Visual Studio.

Many people in non English-speaking countries prefer to write their code and comments in English; I guess it's ok to select the computer's language by default, but there should be an easy way to switch to another language just for Visual Studio (or just for the project).

So, great idea, poor usability.

| January 15 2015

very good, easy to use, many thanks guys!

| January 08 2015

Good idea. But the fact that it does not seems possible to select the language destroys the interest of this plug-in.

by TheFetz | September 17 2014

Should have been included in Visual Studio.

| August 13 2014

| July 02 2014

Very useful

by edsquall | May 13 2014

Funciona como ingles como en español, excelente complemento =)

| January 03 2014

I needed this for a long time :)
nice!

| May 06 2013

| April 18 2013

Good tool.

Would be better if it could underline in something other than red - I find that quite distracting. Green would be better as it usually refers to a warning rather than a critical error.

by Xeffer | March 29 2013

Awesome extension!

One problem is that it spell checks header file paths/names. Could that be removed or made into an option?

#include <stdexcept> // Yeah, I know that is not a dictionary word...

Thanks.

1 - 20 of 102 Items

• Spell Checking SUmmary in bottom window
2 Posts | Last post April 30, 2012
• I was wondering if there was a way (or plan to do so in the future) to have a summary at the bottom saying all the errors of hte current document and/or project. Just like all the errors compiling or when you right click on something and choose 'find all references'.

• It's technically possible to do, but I have no plans of doing it. If you are feeling adventurous, you can find the source here: https://github.com/noahric/spellchecker

-Noah
• Visual Studio 11 Support?
2 Posts | Last post March 24, 2012
• Is there any chance of getting this extension to work with Visual Studio 2011? It's currently in Beta, but I love this extension and would really like to have it installed.
• Apologies, just noticed someone beat me too it below... renaming it to .zip, changing the version number and re-zipping it up works like a charm.
• How to activate
1 Posts | Last post February 29, 2012
• I installed the Spell Checker, it is visible as enabled in Tools / Extension Manager but I still can misspell my comments without getting any hint.
[VS2010 Ultimate, English version]
• Using Spell Checker in english over a german Visual Studio
2 Posts | Last post January 25, 2012
• I'm searching for a way to change the language of Extension for Visual Studio 2010.

The problem is following: I'm using the german language version of Visual Studio 2010. If I use the Spell Checker it checks the correctness in german language, while I'm coding in english. So nearly every single word is underlinded as incorrect.

How can I change the checking language to english or how can I change the libary it used to check language?
• Found the post below. Thanks! :)
I propose to make the language configurable.
• Works great!
2 Posts | Last post January 24, 2012
• I'd like one more option, possibly to ignore works 3 or 4 characters or less.  I often have quick foreach variable names that are 3 or fewer characters long.

Thanks!
• If you're willing to modify the source, that would be a fairly easy change to make.

1) Grab https://github.com/NoahRic/Spellchecker
2) Modify the SpellingTagger.cs:ProbablyARealWord function to exclude words of length <= 4.
https://github.com/NoahRic/Spellchecker/blob/master/SpellChecker.Implementation/Spelling/SpellingTagger.cs#L436
3) Rebuild the extension (in Release mode), find the .vsix in the output directory, and double-click it to install it in VS (as opposed to VS with the experimental hive, which is what you get when debugging the extension in VS).
• Spell Checker support VS11
2 Posts | Last post January 24, 2012
• Hello, any chance this can be updated to support the current VS11 developer preview? Hopefully there isn't much that needs to be done to let it work with VS11.
• I have about 13 extensions to update for VS11 (I haven't even downloaded it yet). Assuming there aren't any actual code changes to be made, you can do it manually in the meantime:

2) Change the file extension to .zip and unzip the contents
3) Modify the extension.vsixmanifest, adding a new entry under the SupportedProducts group:
<SupportedProducts>
<!-- VS10.0 is here, below it add: -->
<VisualStudio Version="11.0">
<Edition>Pro</Edition>
</VisualStudio>
</SupportedProducts>
4) Add everything back to a .zip file, change the extension to .vsix, and double-click it
• How to change the languaje ?
2 Posts | Last post January 24, 2012
• If I want the spell check to be in Spanish, where do I configure this. Thanks :)
• I never added a way of setting that option, so your best bet is to modify the source. Here's how another user did it:

textBox.Language = XmlLanguage.GetLanguage("en-US");

in the SpellingTagger.CheckSpellings method; That works fine for me / in my german environment.
thomas
• How to select language?
3 Posts | Last post January 24, 2012
• Is there an option to change the language that will be used for spell checking? Most of my comments are in English, but some are German (not my fault ;-) ), and I want to check them too without leaving Studio or switching language settings somewhere.

BR, Udo
• PS: I have a German Windows 7 and an English VS 2010, and all spell-checker suggestions are for German. However, I want to use English as language to be checked.
• I never added a way of setting that option, so your best bet is to modify the source. Your case is special since you have a mix of languages, so this may not work terribly well for you, but it is at least an option you should know about :)

Here's how another user did it:

textBox.Language = XmlLanguage.GetLanguage("en-US");

in the SpellingTagger.CheckSpellings method; That works fine for me / in my german environment.
thomas
• Visual studio not responding with spell checker enabled.
2 Posts | Last post January 24, 2012
• With the spell checker enabled I brought in the following text file (output from lint only much larger).  dnvenv.exe was stuck at about 25% and hung.  I finally was able to close the file, turn off the spell checker and open it back up without issue (each of the &lt etc. were a spelling error).  Is there a way to limit the extensions from how much CPU they can take?

<?xml version="1.0" ?>
<doc>

While instantiating boost::property_tree::basic_ptree&lt;std::basic_string&lt;wchar_t,std::char_traits&lt;wchar_t&gt;,std::allocator&lt;wchar_t&gt;&gt;,std::basic_string&lt;wchar_t,std::char_traits&lt;wchar_t&gt;,std::allocator&lt;wchar_t&gt;&gt;&gt;::iterator&lt;std::basic_string&lt;wchar_t,std::char_traits&lt;wchar_t&gt;,std::allocator&lt;wchar_t&gt;&gt;,std::basic_string&lt;wchar_t,std::char_traits&lt;wchar_t&gt;,std::allocator&lt;wchar_t&gt;&gt;,std::less&lt;std::basic_string&lt;wchar_t,std::char_traits&lt;wchar_t&gt;,std::allocator&lt;wchar_t&gt;&gt;&gt;&gt; at File D:\dev\sapphire\marshalling\sapphire_interaction\sapphire\interaction\MessageHelper.cpp line 54
<message><file>D:\dev\sapphire\boost_1_46_1\boost\multi_index_container.hpp</file> <line>324</line> <type>Error</type> <code>330</code> <desc>Static assertion failure: index_found</desc></message>
</doc>
• If you are asking if there's a setting for that somewhere, the answer is no, sorry.

If you are asking, generally, if VS 2010 can do that, the answer is not really. Extensions run in the same process as Visual Studio and as first-class citizens as every other component of VS, so there's not much it can do in general to prevent badly behaved extensions.

This extension uses a background thread at BelowNormal priority to do the work that is eating one of your CPU cores, so it (hopefully) shouldn't be blocking the UI thread directly. However, the work the editor does in response (drawing squiggles, placing smart tags, etc.) is most likely on the UI thread, and some of those things tend to scale super linearly with the number of items.
• Force spell check
2 Posts | Last post January 24, 2012
• Is it possible to force the spell checking of an existing project, maybe see all errors in the Warnings tab instead of scrolling through each code page?

It would also be handy if there was a "Replace All" function so you can correct all the instances of the same error.
• Agreed on both. I'll probably never get around to it for this extension, though, so your best bet would be to find another spell checker extension on the gallery that does that type of thing *and* send feedback (via Connect) that you'd like to see these features in Visual Studio at some point.
41 - 50 of 85 Items