Supported Platforms
Where do applications built with TX Text Control .NET Server run? The summary below answers this question for decision makers and developers who are new to the product: the operating systems for development and deployment, the .NET versions, container and cloud hosting and the web frontends. For the detailed lists, see System Requirements and the Deployment Guide.
At a Glance
| Area | Supported |
|---|---|
| .NET | .NET 8, .NET 9 and .NET 10. The Classic engine is also available for ASP.NET applications on the .NET Framework 4.x. |
| Development | Visual Studio on Windows. The current tutorials use Visual Studio 2026 and .NET 10. Text Control's articles also use Visual Studio Code with the .NET CLI, including on Linux. |
| Deployment operating systems | Windows and Linux |
| Containers and cloud | Docker, Kubernetes, Azure App Services on Linux and Windows, AWS and Google Cloud |
| Web frontends | ASP.NET Core MVC with Razor views, Angular, React, plain JavaScript and Blazor. As legacy platforms on Windows, ASP.NET MVC 5 and ASP.NET Web Forms on the .NET Framework. |
Core or Classic per Platform
TX Text Control .NET Server contains two document processing engines, each in its own NuGet package, and the engine you choose decides where your application can run. Core (TXTextControl.TextControl.Core.SDK) runs on Windows and Linux, including Linux containers, and is recommended for new projects. Classic (TXTextControl.TextControl.ASP.SDK) runs on Windows only and is needed for DOC files. Your code is nearly the same for both engines; Core and Classic in Product Architecture compares them.
Development Environment
You develop on Windows 10 or Windows 11 with Visual Studio, or with Visual Studio Code and the .NET CLI on Windows and Linux. The current tutorials use Visual Studio 2026 and .NET 10. Development Environments lists the tools and their versions, and Operating Systems the development systems.
Deployment Operating Systems
Applications run on Windows, from Windows 10 and Windows Server 2019 on, and with the Core engine on most Linux distributions; Text Control tested Debian and Ubuntu. Operating Systems has the documented list, and the Windows and Linux deployment guides have the steps.
.NET Versions
The NuGet packages target .NET 8, so they work in projects for .NET 8, .NET 9 and .NET 10. ASP.NET applications on the .NET Framework 4.x use the Classic engine from the Windows setup. See .NET Versions.
Containers and Cloud Hosting
The Core engine has no dependency on GDI or on system fonts, so an application that uses it runs in Linux containers and in cloud environments. The following environments are described by Text Control:
| Environment | What Text Control describes | Deployment guide |
|---|---|---|
| Docker | Linux containers based on Microsoft's official .NET images and the Docker templates of Visual Studio. Ultra-minimal Ubuntu chiseled images also work, but they need the gconv system library copied into the image. Windows containers are also supported, as the release announcement of version 33.0 names them. | Docker |
| Kubernetes | Your ASP.NET Core application and the Document Editor backend TXTextControl.Web.Server.Core run in containers and scale out to several instances. The backend can also run on virtual machines or bare-metal servers. | Kubernetes |
| Azure App Services | Deployment to Azure App Service (Linux) with the target runtime linux-x64 and to Azure App Service (Windows) with win-x64. For the Document Editor on Windows, you enable 64-bit and WebSockets in the App Service settings before you publish. | Azure |
| AWS | For example AWS Elastic Beanstalk and AWS Fargate | AWS |
| Google Cloud | For example Google Cloud Run | Google Cloud |
Scaling affects licensing: in the cloud, each running instance of your application, such as a container, a pod or a scaled-out App Service instance, needs a runtime license. For environments that scale automatically, Text Control offers an unlimited runtime (OEM) license. See Licensing Overview.
Web Frontends
The Document Editor and the Document Viewer run in the browser, in an ASP.NET Core MVC view, an Angular or React application, a plain JavaScript page or a Blazor Web App. Every frontend needs an ASP.NET Core backend with TX Text Control .NET Server, which runs on Windows or Linux, because the documents are processed on the server. Frontends and the ASP.NET Core Backend lists the packages of each frontend, npm Packages the Angular and React versions they work with, and Browser Requirements the supported browsers. To build your first application with one of these frontends, start with Document Editor or Document Viewer in Getting Started.
ASP.NET MVC and Web Forms on the .NET Framework
The Document Editor and the Document Viewer are also available for ASP.NET MVC 5 and ASP.NET Web Forms applications on the .NET Framework. These are legacy platforms: they run on Windows only, use the Classic engine installed with the Windows setup and reference its assemblies instead of the engine NuGet packages. In Web Forms, the MVC Document Viewer can be used after adding ASP.NET MVC to the project, as the blog article Using the MVC DocumentViewer in ASP.NET Web Forms shows (2021). ASP.NET on .NET Framework in the Integration Guide compares these platforms with ASP.NET Core and shows how the applications are built, and .NET Framework Applications how they are deployed.
Desktop Applications
Desktop applications with Windows Forms or WPF are not built with TX Text Control .NET Server. Text Control offers them as separate products, TX Text Control .NET for Windows Forms and TX Text Control .NET for WPF.