# Application Licensing

> Check the licensing of a Windows Forms release with TX Spell .NET: full version build, no license keys shipped, redistribution limits and dictionary licenses.

- **Product:** TX Spell .NET for Windows Forms
- **Section:** Documentation
- **Kind:** Topic
- **Path:** TX Spell .NET for Windows Forms > Deployment Guide > Application Licensing
- **513 words**
- **Web URL:** https://docs.textcontrol.com/tx-spell-dotnet-winforms/deployment/licensing/
- **LLMs URL:** https://docs.textcontrol.com/tx-spell-dotnet-winforms/deployment/licensing/llms.txt
- **LLMs-Full URL:** https://docs.textcontrol.com/tx-spell-dotnet-winforms/deployment/licensing/llms-full.txt

---

Shipping an application with TX Spell .NET for Windows Forms requires no license on the user's machine: the license is compiled into your assembly when you build. What the licensing side asks of a release is a short list of checks, so that the application you ship is licensed, doesn't contain anything that must stay with you, and respects the licenses of the dictionaries it carries.

### Before You Ship

- **Built with the full version.** A build made with the trial version shows the trial dialog every fifteen minutes and may not be distributed; [From the Trial to the Full Version](https://docs.textcontrol.com/tx-spell-dotnet-winforms/installation/licensing/development/#from-the-trial-to-the-full-version) shows how to switch.
- **No licensing information in the output.** Serial numbers, license keys, credentials and *nuget.config* files with an API token stay with you; the license travels inside your assembly.
- **Nothing others could develop with.** The runtime files ship because your application needs them, not as a library or SDK for others, and the NuGet packages aren't republished.
- **No license checks removed.** Evaluation notices, license checks and licensing information must not be altered or removed.
- **The dictionary licenses included.** Ship the license files of the dictionaries, hyphenation lists and thesaurus files with them, as [Check the License of Each Dictionary](https://docs.textcontrol.com/tx-spell-dotnet-winforms/dictionaries/hunspell/#check-the-license-of-each-dictionary) describes.

The conditions of royalty-free distribution are on [Application Licensing](https://docs.textcontrol.com/tx-spell-dotnet-winforms/installation/licensing/application/#distribute-royalty-free) in the Installation Guide.

### After the Subscription Ends

A version you obtained during an active subscription stays licensed for building, distributing and deploying applications; [Subscription and Updates](https://docs.textcontrol.com/tx-spell-dotnet-winforms/overview/licensing/#subscription-and-updates) describes what a renewal adds.

### With TX Text Control

TX Text Control is licensed separately, with [its own license agreement and deployment licensing](https://docs.textcontrol.com/tx-text-control-dotnet-winforms/deployment/licensing/llms-full.txt). An application that uses both needs a developer license of each product for every developer, and both products' checks above apply.

### Next Steps

- [Application Licensing](https://docs.textcontrol.com/tx-spell-dotnet-winforms/installation/licensing/application/llms-full.txt): royalty-free distribution and its conditions.
- [Build Servers](https://docs.textcontrol.com/tx-spell-dotnet-winforms/installation/licensing/build-servers/llms-full.txt): licensed builds on build machines.
- [Redistribution Overview](https://docs.textcontrol.com/tx-spell-dotnet-winforms/deployment/redistribution/llms-full.txt): the files that ship with your application.

---

## Nearby

- **Previous:** [Deploying .NET Framework Applications](https://docs.textcontrol.com/tx-spell-dotnet-winforms/deployment/dotnet-framework/llms-full.txt)
- **Next:** [Troubleshooting](https://docs.textcontrol.com/tx-spell-dotnet-winforms/troubleshooting/llms-full.txt)