Online Documentation
- Introducing ASPSpellCheck
- Introduction to ASPSpellCheck
- What's New
- Getting Started
- Installation and Settings
- Installation Process
- Compatibility
- Installing Dictionaries
- Your Custom Dictionary
- Enforcing Spelling Corrections
- The Settings File
- Usage
- Basics
- ASPSpellLink Class
- Properties
- caseSensitive
- checkGrammar
- dictionary
- dialogLanguage
- doneMessage
- externalCSS
- fields
- hideSummary
- ignoreAllCaps
- ignoreNumbers
- ignoreWebAddresses
- javaScriptCallback
- newSentanceOnEachNewLine
- useSession
- ASPSpellPath
- Methods
- buttonHTML
- buttonXHTML
- imageButtonHTML
- imageButtonXHTML
- linkHTML
- spellingCheck
- spellingSuggestions
- url
- Notes for Advanced Developers
- ASP.Net Compatibility
- Caching
- Examples
- Basic SpellCheck
- Server Side Spellchecking
- Language Variants
- Submitting a Form
- Rich Editors
- Licenses & Registration
- Free Trial
- Registering
- License Agreement
Notes on Server Caching
To increase performance, ASPSpellCheck caches data at the ISS Application level. This hugely saves on server processor resources, and takes only a few MB of memory per dictionary.
For this reason, the first time you use a dictionary, or after IIS is restated, the spell checker will take a few seconds to set its self up.
The data is stored in the Application using Keys starting with "ASP_SPELL". You are advised to not try to read or modify these application variables