Licensing Overview
Developers, team leads and buyers who are new to TX Spell .NET for WPF get its licensing model here in plain words: who needs a license, what an application may ship without further fees, what a subscription adds, and how the license gets into your application. The license agreement itself is binding; this summary helps you read it.
The Licensing Model at a Glance
| Question | Answer |
|---|---|
| Who needs a license? | Every developer who develops, compiles or tests with TX Spell .NET |
| What is licensed? | TX Spell .NET for WPF, per developer, perpetually |
| Do applications need runtime licenses? | No. Applications are distributed royalty-free |
| Do build servers need a license? | No, as long as every developer is licensed |
| What does the subscription add? | New versions, service packs, the private NuGet feed and support, for one year |
| Can I try it first? | Yes, with the trial version, which has the full functionality |
TX Spell .NET is a product of its own. It is licensed separately from TX Text Control, including when both are used together.
Developer Licenses
TX Spell .NET is licensed per developer: each developer who uses it for development has a license of their own, which isn't shared or used as a floating license. The license is perpetual: the version you acquired stays licensed after the subscription ends. Development Licenses has the rules and the license sizes.
Build Servers and Code Agents
A build server or CI/CD pipeline, and a code agent that works for a licensed developer, need no license of their own as long as all developers are licensed. Build Servers describes the conditions and how a build gets the packages.
Royalty-Free Distribution
Applications built by licensed developers are distributed royalty-free, to customers and within your company, without runtime fees, as long as they add substantial functionality of their own. Application Licensing lists the conditions, and Redistribution Overview the files that ship.
Subscription and Updates
A license includes a subscription for one year, with all updates, service packs and new major versions, access to the private NuGet feed of Text Control, and technical support. Renew it before it expires, or within 30 days after. After the subscription ends, you keep using the version you have: you may go on building, distributing and deploying applications with it, operate the ones already deployed, and keep the packages you downloaded, including in an internal package repository. Newer versions and access to the private NuGet feed require a renewed subscription.
Service packs replace the setups in your Text Control account and update the private NuGet feed. Service Packs lists the service packs of each version.
Trial Version
The trial version is free and has the full functionality. Its setup is TX Spell .NET for WPF 11.0 Trial.exe. The only difference to the full version is a dialog that reminds the user of the trial every fifteen minutes. A trial version may not be used in production or shipped in an application. Development Licenses shows how to switch to the full version; the code stays the same.
How the License Reaches Your Application
No code is needed: in a .NET 8 project, the NuGet package adds a license file that the build embeds into your assembly, and in a .NET Framework project, licenses.licx compiles the license into it. Development Licenses shows both ways, and Build Servers covers automated builds.
Licenses of the Language Data
The dictionaries, hyphenation lists and thesauri aren't part of the license of TX Spell .NET; each has a license of its own. Redistribution Overview says which ones you may ship and what to include.
The License Agreement
The TX Spell .NET for WPF End User License Agreement applies. You accept it when you install, access or use the product. Text Control offers it for download with the product, as a Word document and a PDF file. For questions about licenses for teams, companies or government, contact the Text Control sales team; the pricing page lists the licenses.