This plugin works as advertised (a free spellchecker, yay!), however in Visual Studio 2010 Ultimate, it causes the editor to peg a CPU core at 100%. In turn, responsiveness from intellisense and the keyboard is quite sluggish. The version notes says the performance was fixed, but as of 2011/06/23 performance is still much to be desired.
Thank you very much. Having come from using other IDEs to using Visual Studio 2010, I wasted 15 minutes finding out there was no spell check in the IDE. What a bummer. Found this and it has worked great. A nice feature, is possible, would be getting it working in the Design view. While I write code, most of my time is spent designing, tweaking, etc.
The new version now works with a non-english OS, like French in my case. While I'm glad that it now shows the spelling error in my French translation, all my code comments are in English, which then make the spell checkers underline everything.
Great tool. But looks like that from time to time it is not checking words in java-doc-like comments in C# /** * This spel error will not be found. */
I know that this type of comments are not suggested by Microsoft but i get used to them. Although Visual Studio have some support for such comments. Like adding a '*' at the beggining of the new line on pressing Enter.
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
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.
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]
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?
Is it possible to change the langue of the spell checker?
I have to write English comments, but my spell checker only checks German.
I’m using VS2010 Ultimate (in English).
Regards
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.
thomas
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).
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:
<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
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.
thomas
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.
thomas
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 < 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<std::basic_string<wchar_t,std::char_traits<wchar_t>,std::allocator<wchar_t>>,std::basic_string<wchar_t,std::char_traits<wchar_t>,std::allocator<wchar_t>>>::iterator<std::basic_string<wchar_t,std::char_traits<wchar_t>,std::allocator<wchar_t>>,std::basic_string<wchar_t,std::char_traits<wchar_t>,std::allocator<wchar_t>>,std::less<std::basic_string<wchar_t,std::char_traits<wchar_t>,std::allocator<wchar_t>>>> 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.
