An editor extension that checks the spelling of comments, strings, and plain text as you type or interactively with a tool window. Extra options are available to control how elements and attributes in XML and MAML files are spell checked.
Resource files are not opened with the text editor by default and Visual Studio doesn't expose a way to spell check items in the resource editor's grid. Use the Open With option to open the file in the text editor and spell checking should work as expected.
The \U issue has been fixed for the next release. It's currently not checking for valid hex digits after what it sees as a \U escape sequence right now. For the other issue deleting the user configuration files appears to correct that issue. See this thread: https://vsspellchecker.codeplex.com/discussions/461432
If you could send me your user configuration files so that I can diagnose the issue I'd appreciate it.
Using a dictionary that matches the language of the text will provide good results with correct words almost always within the first few entries. If you're spell checking a foreign language with the default English dictionary, you aren't going to get good results. The language can be set in the configuration options. You will need to install a dictionary for the language so that it is available (it only comes with an English dictionary by default).
The underline color can be set in the Visual Studio color options (the Spelling Error entry).
See the following documentation pages for all the necessary info: https://vsspellchecker.codeplex.com/documentation
Are only Open Office v2.X dictionaries supported, or are v3+ and newer versions supported as well?
Namely, this particular dictionaries are not recognized (followed instructions, and renamed "sr" to "sr-Cyrl"): http://extensions.openoffice.org/en/project/serbian-cyrillic-and-latin-spelling-and-hyphenation
The files have to be named after a valid culture ID. In this case that appears to be something like sr_Cyrl_BA or sr_Cyrl_CS. I wasn't aware of the additional "Cyrl" identifier part so right now it's only looking for cultures values in the format xx-XX. I'll fix it for the next release.
In the meantime, just rename the files to another valid culture id such as fr_FR (underscore instead of dash too by the way) and then select that language in the configuration dialog.
Thank you for the clarification (dash is a typo, was already using an underscore), it works now with your fake naming workaround.
Btw, most spell checkers use only old Open Office v2.X dictionaries (a lot of languages are missing for that version), so you should probably advertise more that your's can use newer ones...
Are you using VS 2013? If so, it appears that the content type for HTML files may have changed between VS2010/2012 and VS2013. See the open work item for Razor .cshtml files which is probably related: https://vsspellchecker.codeplex.com/workitem/34642
For that one, selecting the Open With option and explicitly choosing the HTML web forms editor works around the problem. I'm close to looking into the issue. I just need to wrap up work on some changes in another project first.
I've been playing around with Visual Studio 2013 Ultimate (final) TypeScript (typescriptlang.org) from Microsoft. Everything I was reading said I should be getting intellisense when editing .ts files and I wasn't. I started disabling my extensions and the one that seems to be the make it or break it is Spell Checker.
Interestingly enough, if I disable Spell Checker restart VS, and enable again it will work with TS files until the next restart.
Great spell checker, however I've had to disable it as it's causing VS2013 to exceed 65% CPU utilization almost all of the time.
I've also noticed (which may be connected to the above issue) that when bringing up the spell checker window, the highlighted word starts jumping up and down the open document as if its continually rescanning, each time highlighting a different word, it doesn't stay highlighted long enough on a word, before it suddenly jumps to another word.
From the Extension and Updates dialog box, uninstall it, restart Visual Studio, and then reinstall it and see if that fixes anything. If there's a problem with a corrupt configuration or dictionary, you can delete the user files which are stored in the "%LOCALAPPDATA%\EWSoftware\Visual Studio Spell Checker" folder.
It's working fine for me and I know several other are using it without issue in VS 2013. It could be some odd combination of setting in your particular case I suppose. If the above doesn't fix anything, can you use Tools | Import and Export Settings to export all of your settings and set the .vssettings file to me so that I can see if that is the case?
Thanks Eric, I will try that and see what happens.
I suspect though that it is more project related than settings based, as I've now tried it with other projects and they are working fine. But I do have a specific project that continually causes the problem.
Once I've done some more investigating I'll let you know.
Hi Eric. I still use the old version will force SpellChecker, reworking what that Russian programmer, because it is possible to use the Russian and English languages at the same time.
Please do use several dictionaries simultaneously.
He performed checks for each word, first in the first dictionary, then in the second.
Can you provide a better example? If I just type etc into a document it doesn't flag it as misspelled whether or not it's followed by a period. If I add an extra "c" it flags it as misspelled and "etc" is a suggested replacement. Choosing that replaces it and it doesn't flag it anymore. Periods never show up as part of the suggestions.
I doubt it could be made to work with the resource editor since if it's the one I'm thinking of it's a grid control of some sort. The spell checker relies on integration with the text editor. That said, you can open the .resx file in the text editor. Right click on the file, select the Open With option and then select the XML (Text) Editor option. The editor will then open and the spell checker will treat it as XML.