Service Packs

A service pack updates a major version of TX Text Control .NET for WPF with bug fixes, and Text Control recommends installing the latest one. Service Pack 5 of version 34.0, released on September 14, 2026, is the current one. For each major version from 34.0 back to 30.0, the tables below give the release dates, the setup and the package version of each service pack, followed by the changes that matter when you build or deploy a WPF application.

How Service Packs Work

• Cumulative. Each service pack contains the updates of the service packs before it. An application on version 34.0 without a service pack only needs Service Pack 5.
• One setup. Since Service Pack 1 of version 31.0, one setup installs the full version and the service packs. It detects whether to update an existing installation or install from scratch, and the setups in your Text Control account are replaced with each service pack. Version 30.0 still had separate service pack setups.
• Package versions. The third number of the package TXTextControl.TextControl.WPF.SDK is the service pack: 34.0.5 is Service Pack 5. Package Overview describes the package.
• Private NuGet feed. Since Service Pack 2 of version 34.0, Text Control also publishes the service packs on its private NuGet feeds. The package from the private feed is meant for build servers and CI/CD pipelines; a development machine that uses the designer needs the setup. See Configuring Package Sources.
• Updating. Run the latest setup on the development machine, then update the package in .NET projects, rebuild and test the application. Installing the Product and Installing and Updating Packages describe both steps.

The announcement of each service pack on the Text Control Blog, linked in the tables, leads to the list of the issues it fixes: the Known Issues page of the major version, such as Known Issues of TX Text Control .NET for WPF 34.0. It groups the fixed issues by service pack, with the ID and the area of each, and lists the issues that are still open. For another major version, replace 3400 in the address with its number, such as 3300. Each announcement covers TX Text Control .NET for WPF together with the other TX Text Control products.

Check the Installed Service Pack

An application reads the version and the service pack it runs with from GetVersionInfo of the TextControl, or of ServerTextControl without a window. Its ServicePack is 0 for the original release. Install a Service Pack shows the code.

Version 34.0

The setup of the current version is TX Text Control.NET for WPF 34.0 with SP5.exe, and the trial setup of version 34.0 was updated on the same day. Each package version of 34.0 contains the same files; a service pack changes no file names.

The Known Issues page of version 34.0 lists 11 fixes for Service Pack 1, 16 for Service Pack 2, 10 for Service Pack 4 and 12 for Service Pack 5, and none under Service Pack 3. Most concern the text filters, above all the PDF and PDF/A export, which version 34.0 changed to tagged PDF; others concern mail merge, images, tables and undo. Document Conversion lists the PDF fixes.

Version 33.0

The latest setup of version 33.0 is TX Text Control.NET for WPF 33.0 with SP3.exe.

Version 32.0

Service Pack 2 changed more than any other service pack of these versions:

• Licensing on .NET. .NET applications no longer use the license compiler or licenses.licx. The package update removes licenses.licx and adds the license file txtextcontrol.wpf.license, which the build embeds into your assembly. Existing licenses keep working, and .NET Framework projects are licensed as before. See Development Licenses and the blog article TX Text Control 32.0 SP2 Licensing Changes: Say Goodbye to licenses.licx.
• Class libraries and user controls. The new static property TextControl.EntryAssembly names the assembly that holds the license, so TX Text Control works in a class library or user control that unlicensed assemblies call. See Application Licensing.
• .NET 6. The libraries of the package target .NET 6 instead of .NET 5. Text Control also announced support for .NET 8 with this service pack; see the blog article TX Text Control Supports .NET 8 in Windows Forms and WPF Applications.
• Unit tests and build servers. NUnit and MSTest are supported, and builds in Azure DevOps work without precompiled licenses. See Build Servers.

The change of the license file requires work in existing projects; Breaking Changes lists it.

Service Pack 3 of version 32.0 extended the merging of images: an image placeholder can be merged with SVG markup as plain XML text, not Base64 encoded. See Images and Barcodes and the blog article Service Pack 3: MailMerge Supports SVG Images.

Version 31.0

The dates are those of the announcements. Service Pack 1 introduced the setup that installs the full version and the service packs alike, and the latest one is TX Text Control.NET for WPF 31.0 with SP4.exe. .NET 5, .NET 6 and .NET 7 projects update their NuGet packages from the package source Text Control Offline Packages after running the setup, then rebuild and test the application.

In versions 30.0 and 31.0, a service pack kept the assembly version and increased only the file version. A .NET Framework application didn't have to be recompiled: deploying the new files was enough.

Version 30.0

Each service pack of 30.0 had a setup of its own, which updated an existing installation of version 30.0.

Next Steps

• Installing and Updating Packages: install a service pack in a .NET project.
• Breaking Changes: the changes of each version that can require work.
• Version 34.0: the features of the current major version.
• Installing the Product: download and run the latest setup.