An editor extension that checks the spelling of comments, strings, and plain text as you type or interactively with a tool window. It can also spell check an entire solution, project, or selected items. Options are available to define multiple languages to spell check agains...
Sorry to say it but, it works for me in both VS2013 and VS2015. I'm just using the standard install of both. Do you perhaps have another package installed that provides TypeScript support? If so, perhaps that's doing something different such that its not reporting spans the same way or in a way the spell checker recognizes. Just a guess.
If you've got spelling errors in the TypeScript files, they should show up when doing a solution/project spell check. That's not affected by the editor's tagger.
Just got this, I love it so far! Great for checking my spellings in <p>'s. This is great, and I am guessing using this will save me at least 5% of my grade that I otherwise would have lost. Thank you EWoodruff!
Great extension and THANK YOU for making it freely accessible. For years I've pulled my hair out searching the code for spelling errors made by myself and other team members. And unfortunately our customers are the ones who caught the typos.
This not only catches our strings but also the comments!
If i could give you more than 5 stars, i would. It's a shame those other folks have not changed their votes. I'm using VS2013 Pro with the latest updates and this works great!
The spell check as you type option seems to work as expected within the editor. Solution/project spell checking currently doesn't work in some web projects and the ".ts" file type isn't recognized by the current release so it'll be spell checked as text if it does work. I plan on publishing an update this weekend that fixes those issues.
For future reference, please post such issues at the project site on GitHub as I'll see and respond to them in a more timely fashion: https://github.com/EWSoftware/VSSpellChecker/issues
Hey, Great Extension! I recently installed the extension for VS 2015 and was wondering if there is an easy keyboard navigation option to cycle through all the errors in a file. So ideally I would start at the top of the file, navigate using the keyboard to the first error, resolve it (either by correcting/ignoring or adding to dictionary) using the Ctrl+'.' keyboard shortcut. Once resolved, I would use the keyboard shortcut to navigate to the next error and resolve it and so on, instead of using the mouse to move to the next error.
The interactive spell checking tool window (Tools | Spell Checker | Spell Check Current Document) is intended for that. It will cycle through all spelling issues letting you correct or ignore them one by one until done.
The latest release also has a solution/project spell checking tool window to handle issues across an entire solution, project, or selected items. Those options are found on the same submenu. See the project wiki for usage details (https://github.com/EWSoftware/VSSpellChecker/wiki).
If installed, you should see the menu options under Tools | Spell Checker. Also, when editing files, any misspelled words should be underlined and a smart tag is available to correct them within the editor. See the project wiki for instructions: https://github.com/EWSoftware/VSSpellChecker/wiki
Hey, first of all thanks for your amazing extension! It works perfectly fine for me except one little issue^ I can't get how to add more Doxygen tags to the globally ignored list.
For example, I'm trying to add "\htmlonly" tag, but it still highlights in the text editor: http://i.imgur.com/7lqgvUD.png
And it works fine if I add "htmlonly", but it feels incorrect since all other Doxygen tags are added with leading backslash and they are get correctly ignored.
Adding it without the leading "\" is correct. If you attempt to do so in the configuration editor, it will remove it. The only time you need a leading slash is if the tag starts with what looks like a valid escape sequence (\a, \t, \f, etc.). In all other cases, the leading slash is treated as a word break and won't skip the following letter. See the ignored words wiki topic for details: https://github.com/EWSoftware/VSSpellChecker/wiki/c592c4d8-7387-47fe-9b79-28bf0168f447
Is there a way to disable the scroll markers of the location of spelling. I would like only to underline the wrong spelled words.
I do not want to see the scroll markers because on some files I do not maintain I have almost a continuous pink line. (Vs 2013 community)
There is no way to turn off the markers for just the spell checker. Visual Studio doesn't provide a way to do that. The only way to turn them off is globally for all such markers by going into Tools | Options | Text Editor | All Languages | Scroll Bars and turning off the "Show errors" option. The side effect is that you won't see markers for syntax errors etc. either.
It appears that XML element 'param' for XML style code comments is being incorrectly marked as spelled incorrectly (this used to be ignored). This happened after I upgraded to VS2015 and downloaded the new extension. This problem did not occur in VS2013. Project is in VB.NET. VS2015 Enterprise.
Can you confirm the issue?
Yes, it is an issue. VS 2015 changed the way the classifier works and it's a lot more specific as to the various parts of the XML comments elements. It'll be fixed for the next release due out soon.
For future reference, please post such issues at the project site on GitHub as I'll see and respond to it in a more timely fashion: https://github.com/EWSoftware/VSSpellChecker/issues
This extension isn't working at all for me. It seems like a really great extension and I'd love to use it, so it's a shame that it's not working. I've tried other spell checkers, but they only have "real time" spell checking, which is bad because it's hard to tell the difference between a syntax error and a spell error in the scroll bar.
So I've tried disabling many extensions which I thought may be causing some sort of impact, but that didn't do anything. I haven't changed the global configuration file at all since I've installed it. I've even tried reinstalling VS Spell Checker, but still nothing. I've only tried C++ files (.cpp and .h) and VB files, but I wouldn't think that would change anything.
When I click on "Spell Check Current Document" I get a window with the following message:
"No text editor is selected, the spell checker is currently disabled, or the file is excluded by filename extension.
Select a text editor or edit the global configuration or the appropriate solution, project, folder, or file-specific configuration to enable spell checking or remove the excluded filename extension."
Has anyone had this problem before? If so, was there a solution? Like I said, I'd really like to use this extension. I love to be able to check spelling errors, but I don't like the way the other extensions do it. I'd really appreciate any help anyone could give me, and I thank you in advance.
Try removing the extension using the extension manager, restart Visual Studio, ensure it's been removed, and then install it again. A couple of people have had an issue where the install or automatic update from the Gallery didn't work correctly in the past and a reinstall corrected the problems they were having.
If the one in the gallery still doesn't work, uninstall, restart, close Visual Studio and use the package available at the GitHub project site (https://github.com/EWSoftware/VSSpellChecker/releases).
Awesome, I got it working! So I did all of what you said, EWoodruff, but it still wasn't working. Then I disabled VSCommands and it finally started working. :) I enabled VSCommands again and VS Spell Checker is still working. Thanks for the reply!
So I found another problem that causes the same behavior. If I change the (global) configuration, specifically the "Spell check as you type" setting, it displays the window with the same message as before. I'd like to only spell check when I explicitly say so, so this is causing an issue.
If you've turned the option off globally, then the tool window will not be useable as it does depend on the editor smart tags. The solution/project level spell checking option is probably what you want but I haven't implemented that option yet.
Hi we have a small team and a large solution with a dozen projects and need to share dictionaries in source control so all developers can have the "company" dictionary so all our internal 'misspellings' (which are words to us) are exempted. Can we accomplish this? Having a second 'personal' dictionary for each user is irrelevant for us so as single devs add words to the dictionary and update the source control, all devs will have the new word they added. Is this something we can accomplish? Where is the custom dictionary file stored on disk? Thank you!
The latest release (v2015.3.1.0) supports solution and project-specific configuration files. In them, you can add settings to define the location of a dictionary checked in with the solution/project. At the solution level, the dictionary would be used by all projects in the solution. At the project level, it would only be used by that particular project.
See the Configuration Files topic (https://github.com/EWSoftware/VSSpellChecker/wiki/Configuration-Files) for information on how the configuration files work and how to add them.
Once you've added the dictionary files and the user dictionary file to the solution/project, add a solution or project specific configuration file depending on your needs, open it and go to the Dictionary Settings page, and define the location of the dictionary files. Keep the relative path when prompted (https://github.com/EWSoftware/VSSpellChecker/wiki/Dictionary-Settings).
Unfortunately this appears to be the cause of disabling a lot of functionality (including Resharper) in VS when it gets an exception, so I had to uninstall it. If I get the exception even with it uninstalled, I will retract this post. The ActivityLog.xml entry follows:
<source>Editor or Editor Extension</source>
<description>System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'TagAggregator'.
at Microsoft.VisualStudio.Text.Tagging.Implementation.TagAggregator`1.GetTags(NormalizedSnapshotSpanCollection snapshotSpans)
Based on the exception I reviewed the code and it does look possible for it to access the aggregator after disposal under some conditions. I haven't ran into it myself nor has it been reported but I've added code to fix that and it'll be in the next release.
In future, rather than posting about problems here, open an issue at the project site on GitHub (https://GitHub.com/EWSoftware/VSSpellChecker/issues). I'll see it and be able to respond in a more timely manner.