How much work does an upgrade of TX Text Control .NET for Windows Forms 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. Between 30.0 and 34.0, versions 30.0, 32.0 and 33.0 brought changes that can require work, one of them with a service pack, and 34.0 changed the PDF output. What each change means for your project, and what to change, is described in one place: Breaking Changes in the Upgrade Guide.

Versions That Require Work

In short: version 34.0 changes no existing API, but tags PDF output by default. Version 33.0 requires .NET 8 or higher, removed the SerializationFormat overloads of the barcode control and renamed files of the package, including the native libraries txkernel.dll, txtools.dll and txic.dll, which carry the major version since then like the format libraries before them (tx33.dll, tx33_tls.dll and tx33_ic.dll in version 33.0). Service Pack 2 of version 32.0 replaced licenses.licx by an embedded license file in .NET projects, and version 30.0 requires the full assembly version in each licenses.licx entry of .NET Framework projects. Version 31.0 has no change that requires work. The Upgrade Guide lists what to check for the version you come from.

Changes to Existing API

The Update Notes of each version list the changes to existing classes, properties, methods and events. Only version 33.0 removed members; the notes of 32.0 and 30.0 name additions that keep existing calls working, and 34.0 and 31.0 have none. The upgrade section of each version page gives its notes:

An upgrade over several versions includes the changes of every version in between, and some changes, such as the licensing of Service Pack 2 of 32.0, arrived with a service pack; Service Packs lists them. Members that still work but will be removed are listed on Deprecated APIs.

Related Pages

Breaking Changes in the Upgrade Guide: each change and what your project has to do.
Upgrading from Previous Versions: the steps to move a project to version 34.0.
Deprecated APIs: obsolete members and their replacements.
Service Packs: the updates between major versions.