How much work does an upgrade of TX Text Control .NET for WPF take? Most versions run existing code unchanged, but some change the target framework of the package, the way a license reaches your application or the files the package brings. The changes of each major version from 34.0 back to 30.0, with what to change in your project, are described in one place, Breaking Changes in the Upgrade Guide, and the list below names the versions that have them.

Versions With Changes

34.0: no change to existing API and the same .NET 8 package as 33.0, but tagged PDF output, PDF/A-3a, a toolbox tab named TX Text Control 34.0 and native libraries named tx34.dll. Test the PDF files your application creates.
33.0: .NET 8 or higher, the removed SerializationFormat overloads of TXBarcodeControl.Load and TXBarcodeControl.Save, and renamed files: TXSVGResources.dll, and the native libraries tx33.dll, tx33_tls.dll and tx33_ic.dll in place of txkernel.dll, txtools.dll and txic.dll.
32.0: licensing without licenses.licx and EntryAssembly in libraries, both since Service Pack 2.
31.0: no change that requires work.
30.0: assemblies no longer registered in the global assembly cache (GAC), which affects licenses.licx.

An upgrade across several versions includes the changes of each version in between, as Breaking Changes in the Upgrade Guide explains. Members that still work but will be removed are listed on Deprecated APIs.

Related Pages

Breaking Changes in the Upgrade Guide: each change in detail, with code.
Upgrading from Previous Versions: the steps to move a project to version 34.0.
Migrating from .NET Framework to .NET: move a .NET Framework project to .NET 8 or higher.
Deprecated APIs: obsolete members and their replacements.
Version 34.0: the new features of the current version.