TX Spell .NET for WPF

Breaking Changes

Topic

The What's New notes of versions 7.0 to 11.0 list no member of TX Spell .NET for WPF that was changed or removed, and none is marked obsolete. An upgrade therefore changes your project, not your code, plus a few behaviors worth testing. The table below gives the short answer for the version you come from; Breaking Changes in What's New describes each change in full.

By the Version You Come From

You come fromChange in the projectTest
10.0Target .NET 8 or higher, then update the package to 11.0.1Nothing new
9.0 or 8.0Update the references, or switch to the packageSuggestions: since 10.0, dictionaries with replacement rules suggest correct forms for words typed without their accents or spelled phonetically
7.0Update the referencesThe suggestions, and user dictionaries that start with the flags WORDCHARS, BREAK or ICONV, which TX Spell .NET applies since 8.0
Earlier than 7.0Target the .NET Framework 4.5 or higher, then update the referencesEverything above

Changes That Require Work and Behavior Changes to Test have the details, and Deprecated APIs confirms that nothing is marked for removal.

When You Upgrade TX Text Control Too

An upgrade of both products brings the changes of both; Update Together With TX Text Control pairs the versions and links the breaking changes of TX Text Control .NET for WPF.