Application Licensing
Your users need no license to run an application built with TX Spell .NET for Windows Forms. The license is compiled into the application when you build it, and the application, with the runtime files of TX Spell .NET, is distributed royalty-free. A few conditions apply to what you ship and how.
Where the License Is in a Built Application
- .NET 8 or higher. The build embeds the license file of the NuGet package into your assembly as a resource.
- .NET Framework. The build compiles the license from licenses.licx into your assembly.
Either way, the license travels inside your assembly, and there is no license file to ship with the application.
Distribute Royalty-Free
You may distribute any number of applications that use TX Spell .NET, to customers or within your organization, without runtime licenses or royalties. The conditions:
- The application adds substantial functionality of its own. TX Spell .NET is not distributed on its own, or as a library, SDK or component that others use to build applications.
- Recipients get no licensing information: no license files, serial numbers, license keys or credentials.
- The application is built by licensed developers.
- The NuGet packages themselves are not republished or repackaged for others. The runtime files your application needs ship with it.
What Ships With the Application
The application ships TXSpell.dll, TXSpell.Windows.Forms.dll and the four language data folders, from the build output or from the Assembly folder of the installation, and no license file. Redistribution Overview lists what ships and what never ships, and Check the License of Each Dictionary the licenses of the dictionaries.
Server and Internal Use
Applications deployed within your organization are covered like applications you sell. TX Spell .NET also runs without a user interface, with the TXTextControl.TXSpell.Core.SDK package, for example in a web application or as the spell checker of the Document Editor of TX Text Control .NET Server; the same royalty-free distribution applies. Checking Text in Code shows such code.
Next Steps
- Development Licenses: how the license reaches your projects.
- Build Servers: building the application on build machines.
- Deployment Guide: publishing and shipping the application.