Service Packs

A service pack updates a major version of TX Text Control .NET Server with bug fixes and smaller additions, and Text Control recommends installing the latest one. For each major version from 34.0 back to 30.0, the release dates and package versions of its service packs follow, together with the changes that matter when you write or deploy code. Service Pack 5 of version 34.0, released on September 14, 2026, is the current one.

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 updated with each service pack. Version 30.0 still had separate service pack setups.
• Package versions. The third number of the SDK packages TXTextControl.TextControl.Core.SDK and TXTextControl.TextControl.ASP.SDK is the service pack: 34.0.5 is Service Pack 5. The web packages, such as TXTextControl.Web, have versions of their own. Package Versioning explains both.
• Private NuGet feed. Since Service Pack 2 of version 34.0, the service packs are published on the Text Control Private NuGet Feed.
• Updating. Update all TX Text Control packages of a project together, rebuild the application and deploy it with the Document Editor backend. Updating NuGet Packages has the steps, and the blog article Service Pack Update Strategy for TX Text Control .NET Server explains the update of an ASP.NET application.

The announcement of each service pack on the Text Control Blog, linked in the tables, leads to the list of the issues it fixes.

Check the Installed Service Pack

An application can read the version of TX Text Control it runs with. Paste the following code into Program.cs of a console application set up as in Create Your First Application:

using TXTextControl;

using (ServerTextControl tx = new ServerTextControl())
{
    tx.Create();

    // Read the version of the TX Text Control assemblies in use
    VersionInfo versionInfo = tx.GetVersionInfo();
    Console.WriteLine($"TX Text Control {versionInfo.Major}.{versionInfo.Minor} SP{versionInfo.ServicePack}");
}

The code works as follows:

• GetVersionInfo returns a VersionInfo object with information about the installed version of TX Text Control.
• Major and Minor are the version numbers, for example 34 and 0.
• ServicePack is the number of the installed service pack. The original version, without a service pack, has the number 0.

Version 34.0

• Web packages. TXTextControl.Web and TXTextControl.Web.DocumentEditor.Backend were released in versions 34.2.0, 34.3.0 and 34.4.0 on the same days as Service Packs 2, 3 and 4. Their current version is 34.5.0. The current TXTextControl.Web.DocumentViewer is 34.2.0, and TXTextControl.Web.DocumentViewer.Classic is 34.0.0.
• System.Drawing.Common. Since Service Pack 1, TXTextControl.TextControl.ASP.SDK depends on System.Drawing.Common 8.0.0 instead of 6.0.0.

Version 33.0

• Document Viewer 33.2.1. Released in July 2025, this version of the Document Viewer package added the zoomChanged event, which Zooming describes. The blog article Document Viewer 33.2.1 Released: New Event and Bug Fixes lists its fixes.

Version 32.0

Version 32.0 has one SDK package, TXTextControl.TextControl.ASP.SDK; the Core engine arrived with 33.0.

• Service Pack 1: the connection ID in server code. The Document Editor's connectionID returns the unique ID of its connection. The blog article How to Manipulate the Document using the WebSocketHandler, written for Service Pack 1, reads it in JavaScript and passes it to server-side C# code that loads and changes the document of that editor.
• Service Pack 2: licensing and .NET 6. .NET applications no longer use licenses.licx: the license file txtextcontrol.server.license is compiled into the assembly, and ServerTextControl.EntryAssembly names the licensed assembly for a class library. This change requires work; see Breaking Changes in the Upgrade Guide. The libraries of the NuGet package target .NET 6 instead of .NET 5, and unit tests and builds in Azure DevOps work without precompiled licenses.
• Service Pack 3: SVG images in mail merge. MailMerge merges SVG images into image placeholders. The data contains the SVG as XML, not as a Base64 string. Images in Mail Merge and Reporting shows the data, and the blog article Service Pack 3: MailMerge Supports SVG Images explains it.
• Service Pack 3: long polling in the Document Viewer. The Document Viewer 32.3.0, which shipped with Service Pack 3, loads documents with long polling: pages appear while the server still renders the rest. See Architecture of the Document Viewer and the blog article Document Viewer: Long Polling Support for Loading Documents.
• Service Pack 4: the Document Editor in single-page applications. The blog article Using the Document Editor in SPA Applications using the removeFromDom Method, which applies to versions after Service Pack 4, removes the editor from a single-page application or an ASP.NET Core partial view with removeFromDom.

The Document Viewer package received further versions between the service packs:

• 32.1.1 (December 2023): users type their signature in a font of their choice, besides drawing it or uploading an image. See Digital Signatures of the Document Viewer and the blog article Document Viewer 32.1.1 Released: Signature Typing Support.
• 32.2.1 (March 2024): support for PDF.js 4.0 and later, with new settings for the paths of the library and its worker. This change requires work when you update PDF.js; see Breaking Changes in the Upgrade Guide.
• 32.3.1 (August 2024): RenderMode selects how the viewer renders pages. See Zooming.
• 32.4.1: members that enable, disable, show and hide the buttons of the viewer's toolbars. See User Interface.

Version 31.0

The dates of Service Packs 1 to 3 are those of their announcements.

• Service Pack 1: one setup. Service Pack 1 introduced the setup that installs the full version and the service packs alike. .NET 5, .NET 6 and .NET 7 applications update their NuGet packages from the Text Control Offline Packages source that the setup installs. See Offline Packages.
• Document Viewer versions. In version 31.0, the minor version of the Document Viewer package names the service pack it belongs to: with Service Pack 1, use a package of the form 31.1.x. The blog article Document Viewer Update: DocumentViewer 31.1.1 Released describes this; version 31.1.1 added events for form fields and an option that keeps the aspect ratio of annotations.
• Document Viewer 31.2.2 (March 2023), for Service Pack 2: the viewer is a Web Component, so a page can hold several instances, it can render PDF documents with PDF.js, it accepts .NET-compatible regular expressions, and its event names are case-insensitive. See the blog article Document Viewer 31.2.2 Final Released: PDF.js, Web Component and Regular Expressions.

Version 30.0

Each service pack of 30.0 had a setup of its own. Applications with the Document Editor also updated the MVC NuGet package, the Angular npm package and, on the server, the files of the TCP backend service, the Windows service that the editor of version 30.0 connected to.

Next Steps

• Updating NuGet Packages: install a service pack in a project.
• Breaking Changes: the changes of each version that can require work.
• Version 34.0: the features of the current major version.
• Package Versioning: how the versions of the SDK and web packages relate.