TX Spell .NET for WPF

Older Versions

Topic

Many features of TX Spell .NET for WPF that applications use today, from the customizable spell check dialog to hyphenation and language detection, arrived between 2012 and 2015. Versions 6.0 back to 3.0 each have a page with their features, their service packs and the classes and members they added, for developers who maintain an application on one of these versions or want to know when a feature appeared.

The versions from 7.0 on are described in What's New, together with their service packs, breaking changes and deprecated APIs.

Versions at a Glance

VersionReleasedReleased withWhat it brought
6.0April 2015TX Text Control X12The SpellingCorrectionUIProvider for correction interfaces built with data binding, Cancel for word changes
5.0September 2014TX Text Control X11Language detection with DetectLanguageScopes for more than 30 languages
4.0November 2013TX Text Control X10Hyphenation with Hunspell hyphenation lists, checking in a given language, right-to-left dictionaries, compressed and delayed loading of dictionaries
3.0September 2012Released on its ownKeyboard-aware suggestion ranking, the customizable SpellCheckDialog, new events, dictionaries from string arrays, GetMenuItems

The dates are those of the release announcements on the Text Control Blog. Text Control released each version for WPF and for Windows Forms on the same day. The download package holds the last setup of each version, usually that of a later service pack, so the dates of its files aren't release dates.

What the Version Pages Contain

Each page starts with the release date and the focus of the version and then describes its features, linked to the pages that explain them for today's version.

  • Service packs. The service packs of the version, with the dates of their announcements and the setup files the download package holds.
  • New classes and members. The classes, properties, methods and events that the What's New documentation of the version lists, grouped by class, each linked to its current reference page. Where that list names a member under a wrong kind or a member the current assemblies don't have, the page says so.
  • Update notes. The What's New documentation of these versions names no changes that break existing code, so the pages have no upgrade section.

Where to Start

  1. Looking for the version of a feature? Start with the table above, then open the version's page. Many reference pages also state the version that introduced a class or member.
  2. Upgrading from one of these versions? Read the pages of the versions you skip, then Breaking Changes for the versions from 7.0 on: since version 7.0, WPF applications require the .NET Framework 4.5 or higher.
  3. New to TX Spell .NET? Start with Version 11.0 and Getting Started instead; these pages describe history.