Licensing Overview
Developers, team leads and buyers who are new to TX Text Control .NET Server get its licensing model in plain words: which licenses your developers need, which licenses you need to run your application in production, what a subscription includes and what the trial version may be used for. How the licenses reach your projects and servers is covered separately in License Configuration.
The Licensing Model at a Glance
| License | What it covers | Who needs it |
|---|---|---|
| Developer license | The use of TX Text Control by one developer. The license is perpetual. | Every developer who uses the product, including testers who compile the application |
| Runtime license | One production server or virtual machine (per operating system), with any number of applications and users | Every production server on which your application runs. In the cloud, every running instance. |
| Unlimited runtime (OEM) license | Deployment to an unlimited number of servers or instances | Applications that are deployed to many servers or scale dynamically in the cloud |
| Subscription | One year of new releases, service packs, updates and technical support | Teams that want new versions and support. Renewing is optional. |
| Trial version | Evaluation of the fully featured product for 30 days | Developers who evaluate the product before they buy it |
Developer Licenses
TX Text Control .NET Server is licensed per developer: every developer who uses the product, including testers who compile your application, needs their own assigned license, and the licenses are perpetual. If five developers work on one application, five developer licenses are required. Per-Developer Licensing describes the rules, including build servers and Linux.
Runtime Licenses
To run your application in production, you need a runtime license for each production server or virtual machine (per operating system); the number of applications and users on that server is not limited. The standard package includes two runtime licenses. In the cloud, each running instance of your application, such as a container, a pod or a scaled-out App Service instance, needs its own license. Runtime Licenses describes how to count them.
Unlimited Runtime (OEM) License
The optional unlimited runtime (OEM) license covers any number of servers and instances, so you do not need to track instances in deployments that scale dynamically, such as AWS Fargate, Azure App Services and Kubernetes. See OEM Unlimited Runtime.
Subscription and Updates
A subscription gives you access to new versions and technical support. For the period of one year, it includes:
- All major releases
- All service packs
- All updates
- Technical support by telephone and email, with an unlimited number of support incidents
When a new version, update or service pack is released, subscribers receive an email that explains how to update.
Renewing a Subscription
- You can renew your subscription for another year before it expires.
- If it has expired, you can renew it within thirty days after the expiry date. After thirty days, the subscription can no longer be renewed.
- Renewing is optional. If you want a current version at a later date, you can upgrade.
When a Subscription Ends
Your license is perpetual, so an expired subscription does not take away what you bought:
- Your deployed applications continue to run as before.
- You can continue to develop, maintain and ship applications with the version you licensed.
- You no longer receive new releases, feature updates, bug fixes and technical support published after the subscription end date.
- TX Text Control does not need an Internet connection or a license server to run your applications.
Trial Version
The trial version is fully featured and valid for 30 days, and it adds a trial text to the documents it creates. It is for evaluation only: Evaluating with the Trial Version lists what the license agreement forbids.
How Licenses Reach Your Application
You do not activate licenses or manage license files by hand: the license comes with the NuGet packages from the Text Control Private NuGet Feed and is compiled into your application when you build it. How the License Gets into Your Project explains the technical details, for example how to use TX Text Control in a class library.
Terms to Know
The license agreement also contains rules for the applications you build:
- Your end users must not be able to modify the program or create programs based on TX Text Control, and they must not be given the TX Text Control serial number.
- Only the files designated as redistributable may be included with your application.
- You must not use TX Text Control to create wrappers or similar constructs with the primary intent of selling or distributing them as a separate library.
The License Agreement
This page is a summary. The license agreement is binding: you accept it when you install TX Text Control, and every NuGet package contains it as LICENSE.md. If you have questions about licensing a specific deployment, for example the number of runtime licenses for your server or cloud setup, the Text Control sales team answers them.