Toolbox and Designer
In a Windows Forms project, you drag the TXSpellChecker component from the toolbox onto a form and connect it to the control whose text it checks. When the component isn't in the toolbox, or spell checking doesn't start after you add it, the cause is usually the package or a missing connection. Visual Studio Toolbox and Designer describes the toolbox when everything is in place.
The TXSpell 11.0 Tab Is Missing
In a .NET project, the toolbox has no tab TXSpell 11.0 with the TXSpellChecker component.
The tab comes from the package TXTextControl.TXSpell.WinForms.SDK, which adds TXSpellChecker to the toolbox. TXTextControl.TXSpell.Core.SDK contains no component and adds nothing to the toolbox.
- Install
TXTextControl.TXSpell.WinForms.SDKfrom Text Control Offline Packages, not onlyTXTextControl.TXSpell.Core.SDK. - Open a form in the designer and look for the tab TXSpell 11.0.
In a .NET Framework project, the setup creates the toolbox tab, and it is available in projects created with the template Windows Forms App (.NET Framework).
The Component Doesn't Appear on the Form
You dragged TXSpellChecker onto the form, but it isn't shown on the form.
TXSpellChecker is a component without a user interface of its own. The designer places it in the component tray below the form, not on the form.
- Select
txSpellChecker1in the component tray to set its properties.
Spell Checking Doesn't Start
The component is on the form, but misspelled words in the TextControl aren't marked.
The spell checker must be connected to the TextControl through its SpellChecker property, and IsSpellCheckingEnabled of the TextControl must be true. Set both in the Properties window, as Connect the Spell Checker in the Designer shows, then build and start the application. If the words are still not marked, the language data may be missing; see Dictionaries Not Found.