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).
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 reading all these language related question I was still unable to understand whether there are any language options without recompiling the code?
I have a German OS, German Office with English dictionary and an English Visual Studio.
The spell checker is set to German which I don't want.
Am I right that this tool cannot provide English spellcheck for my configuration?
You can change the language from the "language button" in Windows 8 taskbar (I think it was called the "language bar" in previous versions). I don't think it appears by default, you have to have multiple languages installed in Windows "Language Preferences" dialog and/or multiple input methods configured.
This may be generic to WFP's Customer Dictionary, but I am not sure,
and in either case I don't know how to accomplish porting your Visual Studio's Spell Checker Dictionary to a new PC. I really do not want to began again teaching it all the words I have added over the past 2.8 years.
Thank you in advance.
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).
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 ;)
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? :)
Yoda86: sadly, it doesn't work at all like that; it's not a matter of just picking what the dependency is. There are other extensions that use the Office dictionary, for example, but the spell checking mechanism is entirely different there, so it's a really different extension. Also, the language packs in visual studio aren't the same things as dictionaries + some grammar support to pick out spell-checkable words in sentences, so that doesn't help either. Sorry :(
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?
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.