License Configuration
TX Spell .NET for Windows Forms is licensed per developer, and applications built with it are distributed royalty-free. How the license gets from your purchase into your projects and applications depends on the project type: in .NET projects, the NuGet package carries it; in .NET Framework projects, a licenses.licx file does. Neither needs code.
How the License Reaches Your Application
| .NET 8 or higher | .NET Framework | |
|---|---|---|
| Where the license comes from | The license file txspell.winforms.license in the NuGet package | The assemblies of the setup |
| What your project contains | Nothing extra: the package adds the file as an embedded resource | An entry for the spell checker in licenses.licx |
| What your build does | Embeds the license file into your assembly | Compiles the license into your assembly |
| What your users need | No license | No license |
A project that uses TX Text Control as well carries both licenses: each package brings its own license file, and in a .NET Framework project, licenses.licx holds entries for both products. TX Spell .NET is a product of its own, licensed separately from TX Text Control.
The Rules in Short
TX Spell .NET is licensed per developer, applications are distributed without runtime fees, build servers need no license of their own, and the trial version is for evaluation only. Licensing Overview explains these rules; the license agreement of TX Spell .NET for Windows Forms is the authority on them, and the pricing page answers common questions about licenses and subscriptions.
Find the Right Page
| If you want to | Read |
|---|---|
| Know how the license file and licenses.licx work, and switch from the trial | Development Licenses |
| Know what may ship with your application and what users need | Application Licensing |
| Build your application on a build server or in a pipeline | Build Servers |
When the trial dialog appears or a license error comes up, see Licensing in Troubleshooting.