Spell Checker

Free

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

(90) Review
Visual Studio
2013, 2012, 2010
Download (206,965)
4/21/2014
2.25
View
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Description
Reviews (90)
Q and A (78)
Sign in to write a review
Sort by:

by TheFetz | September 17 2014

Should have been included in Visual Studio.

by Jasin2069 | August 13 2014

Very helpful

by Shay Dolev | July 02 2014

Very useful

by edsquall | May 13 2014

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

by Piotr Kula | January 03 2014

I needed this for a long time :)
nice!

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

Thanks.

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 |
Delete

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!

SUGGESTION (PLAESE CONSIDER):
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

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


  • Visual Studio 2013
    8 Posts | Last post 7:54 AM
    • Will this be updated to support Visual Studio 2013? 
    • Yup. The project had been locked for some reason (the admins had no idea why, so they unlocked it), so I wasn't able to update it with the rest of my extensions. I'll try to get to it soon (it's all built, just not uploaded).
    • When do you expect you can upload it here?
    • Still "soon" :-/ It's been a very busy few weeks, sorry.
    • Awaiting also!  :)
    • You can try:
      Download extension, extract it with a zip program, edit the extension.vsixmanifest and add VisualStudio Version="12.0" (maybe also add some more versions like premium) and the SupportedFrameworkRuntimeEdition to MaxVersion="4.5". Add this file again to the extension file (using a zip program like 7zip/winzip/winrar)and install ;)
      
      
    • Sorry for the delay. 2.25 should support VS2013. Let me know if you have any problems!
    • Since we can install language packs in VS 2013 to fit our personal liking (e.g. non-English OS, but VS with English GUI), IMHO it would just be logical to change Spell Checker to use this instead of the OS GUI's language.
      
      So, would you mind to change the language dependency from OS to VS? Or implement a way to set this up manually - without downloading and compiling your extension's code? :)
  • cshtml files not supported
    2 Posts | Last post September 25, 2014
    • The spell checker works great in cs files, but how do I get the spell checking to with in cshtml files?
      
      Example: <p>Spellling mstake</p>
      The text is not underlined.
    • Strangely enough, the spell checking is working in some cshtml files, but not others.  
      
      Don't know why.
  • Is there a way to hide spell warning in vertical scroll bar (in map mode)
    1 Posts | Last post September 09, 2014
    • Hi,
      
      Greate extension !
      
      Works well in VS13, but when I open existing project with lots of spellings errors I would like NOT to show each error in my scroll bar (when its in map mode)
      
      How can hide the warnings?
      
      Thanks,
      Guy.
  • Ignore configurations?
    1 Posts | Last post September 03, 2014
    • Is there any way to set up ignore rules?
      
      I get a lot or errors flagged in my #include statements in C++ projects. Would be nice to globally ignore all strings for #include statements.
  • CTP 14
    1 Posts | Last post August 13, 2014
    • Just wanted to sat I manually updated the extension to use CTP 14 and seems to work fine. Thank you for a nice simple and useful extension.
  • ajax:ConfirmButtonExtender
    1 Posts | Last post August 12, 2014
    • Thank you guys for this extender!  It truly is a great asset.
      
      I did notice once thing today though.  It didn't catch the misspelling inside of an ajax:ConfirmButtonExtender's ConfirmText field.  I thought I would pass this on.
      
      Thanks again!
  • RESX support
    1 Posts | Last post July 05, 2014
    • As most of my user text is in RESX file, I'd love to see this working inside the VS RESX editor.
  • Does it work for Workitems/TFS Fields?
    2 Posts | Last post February 10, 2014
    • Does this work for Work Items?  (Ie A PlainText or HTML description field)
    • No, just for the visual studio (code) editor.
  • Changing laguage
    2 Posts | Last post January 16, 2014
    • Hi and thanks for this useful extention.
      
      I'm trying to follow a previous comment that you write but unable to open the source code in Vs2012 in order to set the default language to English instead of my windows env in french.
      
      How can I do this please ?
      
      BR.
    • That probably means you don't have the Visual Studio SDK installed. If you do have it installed and it still isn't working, then I'm not sure what the problem would be. Good luck!
      
      -Noah
  • Ignore spelling ...
    2 Posts | Last post January 03, 2014
    • I comment out code lines from time to time during experimentation, then I got all the squiggly lines for code using "//" commenting out.
      
      "///" Are used for commenting and really need to be spell checked, but maybe double comment out "////" by pressing CTRL K + C twice the spell checker could just ignore checking that since its verbosely commented out?
      
      Thanks any way for great plugin!
    • I probably won't update it for that, though I do understand the frustration. If you are using c++, you could try #if 0ing out the block (my personal preference, since it also plays nicely with comments that are already there and is easy to re-enable by switching to #if 1). Sorry :-/
1 - 10 of 78 Items