Spell Checker


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

(86) Review
Visual Studio
2013, 2012, 2010
Download (187,923)
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Reviews (86)
Q and A (72)
Sign in to write a review
Sort by:

by Piotr Kula | January 03 2014

I needed this for a long time :)

by Ilya Rachinsky | May 06 2013

Please add support for coffee files.

by Triscopic | 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...


by __Sam__ | March 25 2013

Pretty good. Not perfect.

1. Treats the string "\nHello" as the word nHello, which is a mis-spelled word. Would be nice if it could be configured to treat \ as an escape character for C and C++ code.

2. No way to explicitly search a file. If a want to search an entire file for spelling mistakes it's a pain in the @$$ to eye-ball a 10,000 line file for red squiggly marks. Would be nice to have a small GUI with options likes Ignore Word, Ignore All, Add to Dictionary, Change Word, Change All, etc.

3. Doesn't check for duplicate words, which is a nice feature of some spell-checkers.

4. Would be nice to be able to import/export words, with the import/export file format being a list of words separated by lines in a file.

A helpful utility, but not a full replacement for a spell-checker.

by MattHazz | March 25 2013

Much needed! Fast! Custom dictionary entries. Very useful.

by Syncor | March 14 2013

by Amjad Abdelrahman | February 24 2013

It Will be great if the spell checker mark the wrong phrases in other color instead of red it make programer think that somthing wrong with there code

by Dmitry Gurinovich | January 29 2013

Great extension!

by MarkLalor | January 22 2013

Excellent! Just what I was looking for. Thanks

by yuvanti | December 21 2012

Very useful tool. Only way I can think of improving this, it would be nice if it recognised when I was referencing code in comments but that's a minor detail very pleased with this add-on.

by Kevin B Damen | November 14 2012

Excellent extension, I would like to help extend it to additional file formats,

for example .JS,

How can I help, or where can I post a list of what it does wrong? In the Js files it does not like XML Documentation “<param>”

Noah Richards November 26 2012
| Edit |

You can check the source here: https://github.com/NoahRic/Spellchecker

by Paulius Žaliaduonis | November 09 2012

A Must have.

by Emil Tabakov | October 19 2012

This extension saved me so many times. I love it.

by Jozef Habdank | September 21 2012

Great plugin!

The spellchecker should have an option to check inside the class/function/variable names when written in the CamelCaseStyle.

Reason: it is very annoying whne progremmers make extreme mstakes in the function names, which can not be corrected easily because e.g. it is a webserice operation contract etc. This feature would be very useful to prevent this :)

by Mido Banna | September 14 2012

excellent tool

by TiltonJH | August 28 2012

Seems to work just fine, but not in anyway one would expect!

By default it checks the spelling in the language of windows and there is no way to change that, other then maybe reprogramming it yourself.

Once it is programed to either have an settings interface where one can set the language to be used or it just uses the specified language of VS (Options -> Environment -> International Settings -> Language) it might be quiet nice.

Till then this extension is very much useless.

by Nathan Allan | August 17 2012

Fast, simple, and seamless. Don't know how it could be better.

by daschilling | August 16 2012

by theoryman | August 08 2012

1 - 20 of 86 Items   
Sign in to start a discussion

  • 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.
    • 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.
      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:
      1) Download the extension
      2) Change the file extension to .zip and unzip the contents
      3) Modify the extension.vsixmanifest, adding a new entry under the SupportedProducts group:
        <!-- VS10.0 is here, below it add: -->
        <VisualStudio Version="11.0">
      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:
      I've downloaded source (from https://github.com/NoahRic/Spellchecker) and added the line 
      textBox.Language = XmlLanguage.GetLanguage("en-US"); 
      in the SpellingTagger.CheckSpellings method; That works fine for me / in my german environment.
  • 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:
      I've downloaded source (from https://github.com/NoahRic/Spellchecker) and added the line 
      textBox.Language = XmlLanguage.GetLanguage("en-US"); 
      in the SpellingTagger.CheckSpellings method; That works fine for me / in my german environment.
  • 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" ?>
        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>
    • 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.
  • Unable to change spelling in collapsed region
    2 Posts | Last post January 24, 2012
    • Firstly, a great entension - gets my 5*s
      One minor issue:  If I open the file and the region is collapsed, I can see there is a spelling mistake in the region on the scroll bar.  If I now open the region the spelling mistake shows up, however if I press CTRL+. I do not get the menu.  I have to close the file, and reopen it with the region expanded, then it works.
    • Sadly, it's a bug in VS2010 (I don't think it was fixed in SP1, though it should be fixed in the next version). I never figured out a decent way of working around it in the extension. I *think* you can make it work by modifying the line (add + remove a space), which should force the extension to re-check the line and remove/re-add the error.
  • Strings in resx files?
    1 Posts | Last post November 17, 2011
    • Would be nice if it would check string contained in resx files...
  • Spell Checker doesnt work
    11 Posts | Last post September 12, 2011
    • I have tried to install this extension. The installation works well and I also see it in the extensions manager in VS2010 premium. The problem is that nothing happens in my code. I don't see any 'red lines' under misspelled words.
      Do you know what can be the cause? Am I doing something wrong?
    • It doesn't sound like you are doing anything wrong, no.  Just to be sure:
      1) What language are you using?
      2) You have misspelled words *in comments* and they aren't showing up with squiggles, correct?
      3) If you open the fonts and colors dialog (Tools->Options->Environment->Fonts and Colors), do you see an entry under Spelling Error?
    • I have the same problem. 
      I have Microsoft Visual Studio 2010
      Version 10.0.30319.1 RTMRel
      Microsoft .NET Framework
      Version 4.0.30319 RTMRel
      Installed Version: Professional
      Tools->Options->Environment->Fonts and Colors->Spelling Error: foreground color is set to red
      Language of Visual Studio is English. I should use French in comments ecc.
      Anyway nothing happen even if if I write //xxxxxxx in a file .cs 
    • Same here, with pretty much the same setup as Dario (except I am running VS2010 Ultimate). 
    • Same problem here. Visual Studio Professional 2010. IDE and comment language is English. The extension is installed and I see Spelling Error under Fonts and Colors.
    • __M
      Same here, VS 2010 Ultimate SP1, installed, I can see it in Fonts & Colours, but // fla foo bar baz test yxoqa does not result in any red squiggles in C++ code (.h file.)
    • Same for me as well - nothing gets marked as spelling mistakes and extension is loaded as witnessed in Fonts and colors. VS2010 Ultimate SP1, Vista x86 SP1 - I have tried disabling all other extensions (except AnchSVN and Nuget needing admin rights to disable), but still gets nothing.
    • I have the same problem with VS 2010 Premium SP1. The extension is installed but I don't get any spelling errors. Is there any new feedback on this issue?
    • I have on one of my machines the same issue. After debugging Spellchecker i found out that the problem is not with Spellchecker at all. Spellchecker is using WPF TextBox.GetNextSpellingErrorCharacterIndex (http://msdn.microsoft.com/en-us/library/system.windows.controls.textbox.getnextspellingerrorcharacterindex.aspx). On my problematic machine this function returns -1 (no errors found). You can test that very simple with creating a WPF project in VS but a text box and a button on it. The code behind looks like:
         public partial class MainWindow : Window
            public MainWindow()
               this.textBox1.SpellCheck.IsEnabled = true;
            private void button1_Click(object sender, RoutedEventArgs e)
               int i = this.textBox1.GetNextSpellingErrorCharacterIndex(0, LogicalDirection.Forward);
      Now but some misspelled words in the text box and click the button. If you get a -1 spell checking does not work. If it works you get something else.
      I'm still investigating why it does not work, but it looks very much that the problem described in this discussion is not one of this Visual Studio Extension.
    • Spelling : "After debugging Spellchecker I found ..." and "Now put some ....". I'm sorry!
    • Solution: After changing the Default Input Language of Windows to English the problem was fixed. (Because I needed another keyboard I had a different input language. I just installed the foreign keyboard under English and everything works now fine.)
31 - 40 of 72 Items