# Licensing

> Fix license problems of TX Spell .NET for WPF: the recurring trial dialog, txspell.wpf.license and the licenses.licx entries of TXSpellChecker and TXSpell.

- **Product:** TX Spell .NET for WPF
- **Section:** Documentation
- **Kind:** Topic
- **Path:** TX Spell .NET for WPF > Troubleshooting > Licensing
- **505 words**
- **Web URL:** https://docs.textcontrol.com/tx-spell-dotnet-wpf/troubleshooting/licensing/
- **LLMs URL:** https://docs.textcontrol.com/tx-spell-dotnet-wpf/troubleshooting/licensing/llms.txt
- **LLMs-Full URL:** https://docs.textcontrol.com/tx-spell-dotnet-wpf/troubleshooting/licensing/llms-full.txt

---

TX Spell .NET for WPF reaches its license through the NuGet package in .NET projects and through *licenses.licx* in .NET Framework projects. The trial version works like the full version, but reminds the user of the trial with a dialog. The problems below start from what you see. [License Configuration](https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/licensing/llms-full.txt) explains how the license reaches an application.

### A Trial Dialog Appears Every Fifteen Minutes

While the application runs, a dialog box titled **TX Spell .NET Trial Version** appears with this text:

```text
From the functionality point of view, the trial version of TX Spell .NET is identical to the full version. The only difference is that a nag screen will appear every fifteen minutes.
The trial version can be replaced by the full version at any time without you having to change code in your application.
```

The application was built with the trial version of TX Spell .NET, which the setup *TX Spell .NET for WPF 11.0 Trial.exe* installs. Install the full version, install the package or reference the assemblies again, then rebuild and redeploy the application, as [From the Trial to the Full Version](https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/licensing/development/#from-the-trial-to-the-full-version) describes.

### The License File of the Package

In a .NET project, the package adds the license file *txspell.wpf.license* to the project with the build action **Embedded Resource**. When the build isn't licensed, check that the file is still in the project with this build action; don't add the file yourself or copy it from another project. [.NET Projects: The License File](https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/licensing/development/#net-projects-the-license-file) describes the file.

### licenses.licx Needs an Entry for TX Spell .NET

In a .NET Framework project, *licenses.licx* needs an entry for each licensed class you use: `TXTextControl.WPF.Proofing.TXSpellChecker, TXSpell.WPF` for the spell checker, and an entry with the assembly version for `TXSpell` when you use it without a user interface. Add the missing entries and rebuild; [.NET Framework Projects: licenses.licx](https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/licensing/development/#net-framework-projects-licenses-licx) shows both entries and where the file is.

### Related Pages

- [License Configuration](https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/licensing/llms-full.txt): how the license reaches your application.
- [Installation and Package Restore](https://docs.textcontrol.com/tx-spell-dotnet-wpf/troubleshooting/installation/llms-full.txt): installing the packages of the full version.
- [Deployment](https://docs.textcontrol.com/tx-spell-dotnet-wpf/troubleshooting/deployment/llms-full.txt): the files an application ships.

---

## Nearby

- **Previous:** [Toolbox and Designer](https://docs.textcontrol.com/tx-spell-dotnet-wpf/troubleshooting/toolbox/llms-full.txt)
- **Next:** [Dictionaries Not Found](https://docs.textcontrol.com/tx-spell-dotnet-wpf/troubleshooting/dictionaries/llms-full.txt)