Licensing Overview

Developers, team leads and buyers get the licensing model of TX Text Control .NET for Windows Forms in plain words: who needs a license, what you may ship to your users without paying royalties, what a subscription adds, and what the trial version and the Express edition allow. The technical side, how the license gets into your projects and builds, is covered in License Configuration.

The Licensing Model at a Glance

Developer Licenses

TX Text Control .NET for Windows Forms is licensed per developer, not per company, team, machine or concurrent user:

• Each developer who develops, maintains, tests or otherwise works with the product needs their own assigned license. A license cannot be shared or used as a floating license.
• You may reassign a license when its developer stops using the product for good.
• The license is perpetual and valid worldwide for the version you licensed. You may build any number of applications with it.
• Build servers and CI/CD systems do not need a developer license of their own, as long as every developer is licensed and the build environment is not used for interactive development.
• Code agents and AI tools that act for a licensed developer do not need a license of their own, but they do not reduce the number of licenses your developers need.

For example, if five developers work on an application that uses TX Text Control, five developer licenses are required. The Professional and Enterprise editions are sold as single developer and team licenses. Editions and Feature Availability compares them.

Royalty-Free Distribution

Unlike TX Text Control .NET Server, the Windows Forms product needs no runtime licenses. Applications built by licensed developers are distributed royalty-free:

• You may distribute and deploy any number of compiled applications, to customers, partners and other third parties and for your own internal use.
• The number of installations, end users and client machines is not limited, and there are no runtime fees or royalties.
• Only the runtime files that Text Control designates as redistributable may be shipped with your application. Redistribution Overview lists them.

When you distribute an application to others, the license agreement requires that:

1. Your application adds substantial functionality beyond that of TX Text Control.
2. It does not ship TX Text Control as a standalone library, SDK or component.
3. Its users cannot build their own applications with TX Text Control through it.
4. Its users do not receive your serial numbers or license keys.
5. It is built by licensed developers.

The NuGet packages may be used in your builds and CI/CD pipelines and mirrored in an internal feed for your licensed developers and build systems. They must not be republished or repackaged for third parties.

Subscription and Updates

A subscription gives you new versions and technical support for one year. It includes:

• All updates and service packs
• New major versions
• Technical support by email, telephone and chat, with an unlimited number of support incidents
• Access to the Text Control Private NuGet Feed

You can renew a subscription for another year before it expires, or within thirty days after it has expired. After that, it can no longer be renewed.

When a Subscription Ends

Your license is perpetual, so an expired subscription does not take away what you bought:

• You can continue to develop, maintain and build applications with the versions you licensed while the subscription was active.
• You can continue to distribute and deploy them royalty-free, and applications already deployed keep running.
• Packages you obtained during the subscription may still be used.
• Versions released after the subscription expired and technical support are no longer included.

Trial Version and Express Edition

• The trial version is fully featured, free for 30 days and needs no serial number. It may be used for evaluation and testing only: not in production, not to provide services to others and not in a commercial application. Evaluation notices and limitations must not be removed.
• The Express edition is free for private and non-commercial use only and comes with its own license agreement. Applications built with it may be distributed royalty-free. Commercial use, such as use by or for a company, in a paid project or for any activity that earns revenue, requires a commercial license. Express has no guaranteed right to updates or technical support, and Text Control may change or discontinue it at any time. See Editions and Feature Availability for its features.

How the License Reaches Your Application

There are no activation dialogs and no license server. In .NET 8 or higher projects, the license file of the NuGet package is embedded into your assembly when you build; in .NET Framework projects, the license compiler embeds it from the entries of licenses.licx. Development Licenses describes both ways, Application Licensing the license in class libraries and user controls, and Build Servers the builds in CI/CD pipelines.

Terms to Know

The license agreement also forbids, among other things:

• Reverse engineering TX Text Control, or removing its license checks and notices
• Disclosing serial numbers or license keys
• Making TX Text Control available to developers who are not licensed
• Building a library, SDK or component that offers substantially the same programming functionality to other developers

The License Agreement

The summary above is not the agreement. The license agreement is binding: you accept it when you install TX Text Control, and the number of licenses and the subscription period are those of your order. The current agreement for TX Text Control .NET for Windows Forms is dated August 11, 2026. If you have questions about licensing a team, a project or a large number of developers, the Text Control sales team answers them.

Related Pages

• License Configuration: how development licenses and application licenses are applied technically.
• Editions and Feature Availability: the Enterprise, Professional and Express editions.
• Application Licensing: the license in the applications you deploy.
• Licensing in Troubleshooting: solve license problems in development and deployment.