Upgrade Guide
Whether an application you maintain uses the current NuGet packages or an older setup-based version of TX Text Control, the Upgrade Guide moves it to a newer version of TX Text Control .NET Server.
An upgrade usually touches more than one place: the NuGet packages of your .NET projects, the npm packages of an Angular or React frontend, the Document Editor backend and, for major versions, some code or project settings. The pages in this section cover each of these steps, list the changes that require action for each version, and describe typical migration paths from older versions.
Kinds of Updates
TX Text Control .NET Server receives three kinds of updates:
| Update | What it contains | How you recognize it |
|---|---|---|
| Major version | New features and fixes. It can contain changes that require code or project changes. The current major version is 34.0, introduced in November 2025. | The first number of every package version changes, for example from 33.0.3 to 34.0.0. |
| Service pack | Bug fixes and minor updates to many components. Text Control recommends that you update your applications to the latest service pack. | The third number of the SDK package version is the service pack: TXTextControl.TextControl.Core.SDK 34.0.5 is Service Pack 5. |
| Web package update | New features, improvements and fixes for the web components. The Document Viewer, for example, receives new features outside of the major release cycle. | The web packages have their own minor versions within the major version, for example TXTextControl.Web 34.5.0 and TXTextControl.Web.DocumentViewer 34.2.0. |
The major version of the SDK and web packages always matches the product version. Package Versioning explains the version numbers and lists the current version of each package.
What a Subscription Includes
New major versions, service packs and updates come with a subscription, which runs for one year and can be renewed; the licenses themselves are perpetual. Subscription and Updates in the Licensing Overview describes what a subscription includes and how it is renewed. The Text Control Private NuGet Feed only shows the packages and versions that you are licensed for. For questions about renewals and upgrade options, contact the Text Control sales team.
Recommended Upgrade Procedure
- Find your current versions. Look up the TX Text Control package versions in your project files and in the
package.jsonof your frontend. - Read the breaking changes. For a major version upgrade, read the Breaking Changes of every version between your current and your target version.
- Check the requirements. Since version 33.0, the NuGet SDK packages require .NET 8 or higher. See System Requirements.
- Update the NuGet packages together. Update the SDK package and all web packages to the same major version. See Updating NuGet Packages.
- Update the npm packages. Use the version of the Angular or React packages that matches the major version of your backend. See Updating npm Packages.
- Apply the required code changes, rebuild and test. Test your application with the new version before you deploy it.
- Redeploy. Deploy the application together with the Document Editor backend. See the Deployment Guide.
Where to Start
| If you want to | Read |
|---|---|
| Install the latest service pack or web package version | Updating NuGet Packages |
| Update an Angular or React frontend | Updating npm Packages |
| Find out which changes a major version requires | Breaking Changes |
| Move from 33.0 to 34.0, from assembly references to NuGet, from the .NET Framework, from Classic to Core or from the old Document Editor service | Migrating from Previous Versions |
| See the new features of the current version | What's New in Version 34.0 |