License Configuration

How does the license get into a TX Text Control .NET Server project, what does each developer need and what do you need when you deploy? The answers matter to developers who set up a project and to anyone who plans a deployment.

For the licensing model itself (developer licenses, runtime licenses, the OEM license and subscriptions), read the Licensing Overview first. The pages in this section focus on what you do with your licenses.

How Licensing Works

TX Text Control .NET Server uses two kinds of licenses: developer licenses, one for each developer who uses the product, and runtime licenses for the production servers your application runs on, or the optional unlimited runtime (OEM) license. Technically, the license comes with the NuGet packages and is compiled into your assembly when you build the project. You do not enter a license key in code, there is no activation dialog, and TX Text Control does not require a cloud-based licensing service or periodic online validation to keep your applications running.

This documentation explains the technical side and does not replace the license agreement, which is binding, as The License Agreement describes. For questions about a specific deployment, contact the Text Control sales team.

What You Need to Do

1. Assign a serial number to each developer. In Manage Products, assign a serial number to the email address of every developer who works with TX Text Control. See Development Licenses.
2. Install packages that contain the license. Each assigned developer installs the packages from the Text Control Private NuGet Feed, which injects the license into the package before the download. Alternatively, the setup provides the packages in the local package source Text Control Offline Packages.
3. Build your application. No further license configuration is needed in most projects. If TX Text Control is used in a class library or in unit tests, set the entry assembly as described in Development Licenses.
4. License your production servers. Before you deploy, make sure that you have a runtime license for each production server, or an unlimited runtime (OEM) license. See Runtime Licenses.

Evaluating With the Trial Version

If you do not have a license yet, you can evaluate the product with the trial version. The Windows setup installs TX Text Control .NET Server and a local NuGet package source named Text Control Offline Packages, from which you install the packages into your projects.

• The trial version is fully featured and valid for 30 days.
• The trial version adds trial text to the documents it creates.
• The trial version is intended for evaluation only.

The license agreement (section 9) forbids the following for the trial version:

• installing it on a production server
• distributing or selling an application with it
• deleting the trial text that is added to the created documents
• using it for development tasks other than evaluation

To try the Document Editor and Document Viewer client packages for Angular or React without installing anything, you can instead request a 30-day trial token for a backend hosted by Text Control. For your own backend, you need the trial version or a license.

When you buy a license, replace the trial packages with licensed packages and rebuild your application. Development Licenses explains how to tell them apart.

Choose a Page