Home > Upcoming, Visualization > Spell checking the entire solution

Spell checking the entire solution

April 9th, 2012
NOTE: please take into account the “Versions” field at the bottom of the post, to determine the build number for which the content is applied. Click here to see the latest officially released version.

In addition to the usual Spell Checker CodeRush feature, you can find and review spelling errors from the entire solution in the dedicated Spell Checker tool window:

CodeRush Spell Checker tool window in the DevExpress Menu

CodeRush Spell Checker tool window preview

Note that the Spell Checker feature must be enabled to perform a solution spell checking operation (enabled on the Spell Checker options page in the Options Dialog).

The tool window contains three toolbar items:

Button caption


Spell check solution Runs a spell check analysis for the entire solution
Edit custom dictionary Opens a custom dictionary where you can specify custom words.
Options Opens the Spell Checker options page in the Options Dialog.

The other part of the window shows a grid with the spelling errors: the text with an error and the file containing one. At the bottom of the tool window, you can see the preview code where the misspelled word was discovered.

Via the right click context menu, you are able to fix all similar misspelled words at once, fix a particular typo with the suggested correction, navigate to a misspelled word or add it to a dictionary:

CodeRush Spell Checker tool window preview with context menu

Products: CodeRush Pro
Versions: 12.1 and up
VS IDEs: 2008 and up
Updated: Apr/10/2012
ID: U011

Similar Posts:

  1. Tom Gez
    April 15th, 2012 at 03:53 | #1


    I wanted to add, on the subject of spell checking, that there is a good program I use, called Spell Check Anywhere, that adds spell checking to all of Windows.

    I know you are talking about here spell checking the solution, but I thought I’d mention a general purpose spell check for all Windows programs… for those interested in spell checking.


  2. April 16th, 2012 at 00:31 | #2

    Hi Tom, thanks for joining in.