Spell-check code, comments, strings, HTML, XML, resources, and general text in Microsoft Visual Studio 2010 as well as Visual Studio 2008 with ComponentOne IntelliSpell™. Benefit from using ComponentOne IntelliSpell, featuring:
•Specify File Types to Spell-check
The Options dialog box
can now be used to specify the types of files that should be spell-checked. You
can specify, for example, that files with extension "licx" should be checked as
XML, and that files with extension "doc" should be checked as text.
•Spell-check Your Entire Visual Studio Project
Spell-check
multiple files, your projects, or your entire solution. IntelliSpell provides an
easy-to-use, one-click operation.
•As-you-type Spell-checking
Spell-checking your Visual Studio
application is even better with as-you-type spell-checking functionality. You
can easily correct spelling errors in files (HTML, XML, resource, text) and code
(comments, strings) as-you-type.
•Choose From a Wide Selection of Dictionaries
IntelliSpell comes
with English-US dictionary as well as 20 additional dictionaries. Plus, you can
customize any dictionary or create a text file to define custom words to ignore
by the spell checker.
•You No Longer Have to Rely On an External Spell
Checker
IntelliSpell has its own spell-checking engine and does not rely
on Microsoft Office spelling services. No longer do you have to have Microsoft
Office installed or import/export documentation to solve this problem.
•Complete XML and HTML and Spell-checking in the Source
Code
Help documentation, based upon XML documents, typically required an
intermediate process of importing to a word processor for spell-checking. Then
corrections were made back in the source code. IntelliSpell eliminates this
tedious and error-prone process.
•Spell Correction is Easy with the Task List
All spell-checking
data can easily be tracked within your application (wiggly underlines), or
within the Task List (line item spelling mistakes). This makes it easy to run
through corrections for an entire project. Simply double-click the spelling
mistake in the Task List to open the Visual Studio file containing the spelling
error; you do not have to search through pages of code to find spelling
mistakes.