Frequently Asked Questions

Q: Which .NET versions and Windows versions are supported?

For traditional ASP.NET: .NET 4.5, .NET 4.8. Supported Windows include Server 2012–2022. For ASP.NET Core/Core SDK: .NET 8 and .NET 9. Windows Server 2019/2022/2025 and most major Linux distributions.

Question 1

Can I deploy TX Text Control .NET Server on Linux?

Accepted Answer

Yes. The product supports deployment on Linux distributions including Debian, Ubuntu, CentOS, and Red Hat — as well as on Azure App Services.

Question 2

Does it run in Docker containers or other container environments?

Accepted Answer

Absolutely. TX Text Control supports Docker and other container platforms. In fact, the backend is cross-platform, containerizable, and deployable on Linux, Windows, Azure App Services, Kubernetes, etc.

Question 3

Is it compatible with .NET 10?

Accepted Answer

Yes. Version 33.0 of TX Text Control has been tested and confirmed compatible with .NET 10 Preview, including running inside Ubuntu-based containers.

Question 4

Can I deploy to Azure App Services?

Accepted Answer

Yes. Azure App Services is supported as a deployment destination.

Question 5

Which .NET versions and Windows versions are supported?

Accepted Answer

For traditional ASP.NET:

.NET 4.5, .NET 4.8. Supported Windows include Server 2012–2022.

For ASP.NET Core/Core SDK:

.NET 8 and .NET 9. Windows Server 2019/2022/2025 and most major Linux distributions.

Question 6

How can I evaluate TX Text Control .NET Server?

Accepted Answer

You can evaluate the product in two ways:

By downloading the full trial version or by requesting a trial token.

Both options allow you to explore the features and integrate TX Text Control into your environment.

Question 7

What is the difference between the download trial version and the trial token?

Accepted Answer

The download trial version is a local installation that includes all assemblies, redistributables, sample applications, and documentation. It is ideal if you want to explore the product in depth on your development machine.

A trial token is a license key that unlocks all product features without installing the dedicated trial version. You use it with the official NuGet packages and evaluate TX Text Control directly in your own project environment.

Question 8

When should I use the download trial version?

Accepted Answer

Download the trial version to test all of TX Text Control's features, including server-side, non-UI processing, the document editor, and the document viewer. Host your own backend to try this out.

Question 9

When should I use a trial token?

Accepted Answer

Use the trial token if you prefer to integrate TX Text Control Document Editor and Document Viewer into your own solution immediately without downloading an installer.

Question 10

Is there support via NuGet packages?

Accepted Answer

Yes. The product offers NuGet packages for easy installation, deployment, and updates. It includes bundled dependencies, configuration options, and simplifies publishing workflows.

Question 11

What is the difference between the Core SDK and the ASP SDK packages?

Accepted Answer

TXTextControl.TextControl.ASP.SDK contains all files compatible with Windows-only environments.

TXTextControl.TextControl.Core.SDK targets a platform-independent version (e.g., for Linux or cross-platform use).

Question 12

What is TXTextControl.Web.Server.Core?

Accepted Answer

This is a lightweight, cross-platform .NET backend serving as the sync server for the Document Editor component. It supports Linux and Windows, and can run as a standalone app, Windows service, or Linux daemon.

Question 13

Can I edit documents via a browser?

Accepted Answer

Yes. The product includes a rich, MS Word–like document editor (HTML Canvas–based) with a full JavaScript API, and a clean document viewer with annotation, form filling, and electronic signature functionality.

Question 14

Can I perform server-side document automation?

Accepted Answer

Yes. TX Text Control allows server-side operations like generating, merging, and converting documents (e.g., merging JSON data into templates, generating PDFs, Office Open XML, RTF, PDF/A-3b forms) without UI.

Question 15

Is a license required for deployment in production?

Accepted Answer

Yes. You need runtime licenses for each production server where your application runs. Full deployment rights are typically included in an OEM license.

Question 16

What is the licensing model?

Accepted Answer

Licenses are per-developer and perpetual — each developer compiling the app needs a valid license.

All licenses include updates and unlimited technical support for the subscription period.

Server & Web

Windows Forms

WPF

ActiveX

Core Technologies

​

Latest Posts

​

Support

Getting Started

​

Other Resources

Company

Contact

Newsletter

Legal

Text Control Account

​

​

High Performance Document Processing for Web and Server Applications

Elevate your applications with enterprise-grade processing for generating, editing, converting, and securing Microsoft Word-compatible DOCX and PDF documents at scale.

Why do you need TX Text Control?

AI-Ready Document SDK

Docker and cloud ready

Perpetual licenses

Powerful API

High performance

30+ Years of Enterprise Trust

Cross-platform

True document editing

One SDK. Every document workflow.

MS Word / DOCX capabilities

Mail Merge capabilities

PDF capabilities

E-Sign capabilities

Document Editor capabilities

Document Viewer capabilities

Rich document editing

Document viewing and collaboration

Powerful APIs for developers

Reporting and mail merge

Electronic signatures

Adobe PDF document processing

Designed for developersDesigned for devs Ready for AI

MCP Server MCP

Agent Skills Skills

Angular, React, ASP.NET Core, or JavaScript

ASP.NET Core

Angular

Blazor

JavaScript

React

Product FAQ

Start a free 30-day evaluation today!

Designed for developersDesigned for devs
Ready for AI