TX Spell .NET for WPF

Upgrade Guide

Topic

Moving an application to TX Spell .NET for WPF 11.0 with Service Pack 1 takes one of three paths, depending on where it comes from: a service pack of version 11.0, an earlier major version, or the .NET Framework. The code of your application rarely changes, because the What's New notes of versions 7.0 to 11.0 list no member of TX Spell .NET that was changed or removed. What changes is the project: the packages or references, the target framework, and sometimes the license entries.

Choose Your Path

You come fromWhat you doRead
Version 11.0 without the latest service packRun the latest setup; in a .NET project, update the package to 11.0.1Service Packs
Version 10.0, 9.0, 8.0 or 7.0Install the setup of 11.0, then update the packages or referencesUpgrading from Previous Versions
A .NET Framework application that moves to .NET 8 or higherReplace the references and the license entries with the NuGet packageMigrating from .NET Framework to .NET

Before You Upgrade

  • Your subscription. New major versions and service packs are included while your subscription is active. A version you obtained during the subscription stays licensed after it ends, but versions released later are not included without a renewal.
  • The target framework. The packages of version 11.0 need .NET 8 or higher. The package of version 10.0 installed in projects for .NET 5 and later, so a project on .NET 5, .NET 6 or .NET 7 changes its target framework first.
  • TX Text Control. When your application uses TX Text Control as well, plan both upgrades together. TX Spell .NET 11.0 was released together with TX Text Control 33.0 and is used with 34.0 in this documentation; Update Together With TX Text Control has the details.
  • What changed. Breaking Changes lists what to check for the version you come from.

Pages in This Section