TX Text Control .NET Server

Operating Systems

Topic

Development machines and production servers can run several operating systems with TX Text Control .NET Server 34.0, and each platform needs a particular engine. Check both before you set up a development machine or choose where your application runs.

Core or Classic Decides the Platform

TX Text Control .NET Server ships with two engines, each in its own NuGet package, and the engine determines the operating systems and processor architectures your application can run on. The Core engine (TXTextControl.TextControl.Core.SDK) runs on Windows and Linux, including Linux containers, and is recommended for new .NET 8 or higher projects. The Classic engine (TXTextControl.TextControl.ASP.SDK) runs on Windows only; use it for Windows-only applications, existing Classic integrations and the legacy Word binary format (DOC). Core and Classic in Product Architecture compares the engines.

Development Machine

Windows

The requirements documentation lists Windows 10 and Windows 11 as development systems. On Windows, you can use Visual Studio, Visual Studio Code or the .NET CLI, and both engines are available.

The trial setup is a Windows installer, so you need a Windows machine to evaluate the product with the trial version. For .NET 8 or higher projects, licensed developers install the packages from the Text Control Private NuGet Feed and do not need a setup.

From Visual Studio on Windows, you can also run a Core application on Linux: select WSL (Windows Subsystem for Linux) as the startup profile, or enable container support with Linux as the container OS when you create the project. See Development Environments.

Linux

The Core engine runs on Linux, so you can also create, build and run applications on a Linux machine with the .NET SDK, the .NET CLI and an editor such as Visual Studio Code. Install the packages from the private NuGet feed with your nuget.config file. The Classic engine is not available on Linux.

Classic ASP.NET on the .NET Framework

For ASP.NET applications on the .NET Framework, which use the Classic engine from the Windows setup, the requirements list Windows 10, Windows 11, Windows Server 2016, Windows Server 2019 and Windows Server 2022 as development systems. The same systems are listed for the servers these applications run on, and the requirements name these system components:

  • The Microsoft Visual C++ runtime. TX Text Control uses VCRUNTIME140.DLL, which the Microsoft Visual C++ Redistributable for Visual Studio 2017 installs, in its 32-bit (x86) or 64-bit (x64) version to match the build of your application. The TX TextControl Service, which the Document Editor uses in these applications, needs the x64 version. The same redistributable package covers Visual Studio 2017, 2019 and 2022, which is why the Deployment Guide calls it the Visual C++ Redistributable for Visual Studio 2017, 2019 and 2022.
  • The Microsoft XML parser. TX Text Control's XML features need MSXML3.DLL, MSXML3A.DLL and MSXML3R.DLL (version 8.00.7820.0) in the Windows system directory. If you redistribute them, Microsoft's redistribution policy applies.
  • A web server. Internet Information Server (IIS) 7.0 or higher. With the Document Editor, IIS 8.0 or higher with the WebSocket Protocol feature installed.

The supported .NET Framework versions are listed in .NET Versions. .NET Framework Applications in the Deployment Guide describes which files you copy to the server and how you install the TX TextControl Service.

Deployment

Windows and Windows Server

The requirements documentation lists the following Windows versions for deployment:

  • Windows 10
  • Windows 11
  • Windows Server 2019
  • Windows Server 2022
  • Windows Server 2025

Both engines run on these systems. The release announcement of version 33.0 also names Windows Server 2016 and Windows containers.

The Classic engine uses the fonts installed on the server. Newer systems such as Windows Server 2025 often do not come with a full set of fonts, so you may have to install the fonts your documents use. The Core engine uses the fonts in its Fonts folder instead.

Linux

Linux requires the Core engine. The requirements documentation states that most Linux distributions and cloud services are supported and lists Debian and Ubuntu as tested. For the Document Editor, it names Debian, Ubuntu, CentOS and Red Hat as examples of supported destination systems. According to the announcement of Linux support in version 33.0, TX Text Control was tested on Ubuntu (LTS and latest stable releases), Debian, CentOS and Ubuntu Chiseled, and runs, from a technical point of view, on any Linux distribution that runs the .NET runtime.

On Linux, you publish the application for linux-x64, and the Core package brings its own Fonts folder, so you don't install system fonts. Minimal container images such as Ubuntu chiseled images lack the gconv library that TX Text Control uses, so you copy it into the image. Linux Requirements in the Deployment Guide describes the target system in detail.

Containers and Cloud Services

With the Core engine, applications run in Linux containers, including Kubernetes, and Windows containers are supported as well. Text Control describes deployments to Azure App Services on Linux and Windows, AWS Elastic Beanstalk and Google Cloud Run. Containers and Cloud Hosting in Supported Platforms lists what Text Control describes for each environment, with a link to its deployment guide. In cloud environments, each running instance counts for runtime licensing; see Runtime Licenses.

Processor Architectures

The Core package contains native libraries for win-x64 and linux-x64, the Classic package for win-x64 and win-x86, as Engine Packages lists. The packages contain no native libraries for other runtime identifiers, for example for macOS or ARM64 processors. The publishing instructions for .NET 8 or higher applications use win-x64 or linux-x64 as the target runtime. The Core engine has no 32-bit files: see The Application Runs as a 32-Bit Process.

Classic ASP.NET applications on the .NET Framework use the 32-bit or 64-bit files of the Windows setup, depending on the build configuration of the project (x86, x64 or Any CPU). Choose 32-Bit or 64-Bit explains which set of files each configuration needs and how to create the configurations in Visual Studio.

Next Steps