# Development Licenses > Per-developer licenses for TX Spell .NET for Windows Forms: the txspell.winforms.license file, licenses.licx entries for TXSpellChecker, and trial to full. - **Product:** TX Spell .NET for Windows Forms - **Section:** Documentation - **Kind:** Topic - **Path:** TX Spell .NET for Windows Forms > Installation Guide > License Configuration > Development Licenses - **799 words** - **Web URL:** https://docs.textcontrol.com/tx-spell-dotnet-winforms/installation/licensing/development/ - **LLMs URL:** https://docs.textcontrol.com/tx-spell-dotnet-winforms/installation/licensing/development/llms.txt - **LLMs-Full URL:** https://docs.textcontrol.com/tx-spell-dotnet-winforms/installation/licensing/development/llms-full.txt --- Every developer who builds applications with TX Spell .NET for Windows Forms needs a developer license of their own. Technically, the license reaches a project through a license file in the NuGet package or, in .NET Framework projects, through an entry in *licenses.licx*. What follows covers both, and the move from the trial version to the full version. ### One License per Developer Each developer who uses TX Spell .NET for development needs a license of their own, assigned to them; [Developer Licenses](https://docs.textcontrol.com/tx-spell-dotnet-winforms/overview/licensing/#developer-licenses) explains who counts, how licenses are reassigned and what stays licensed after the subscription ends. ### .NET Projects: The License File The NuGet package `TXTextControl.TXSpell.WinForms.SDK` contains the license file *txspell.winforms.license*. When you install the package, NuGet adds the file to the project with the build action **Embedded Resource**, and every build embeds it into your assembly. Nothing else is needed: no *licenses.licx* and no code. - **Leave the file in the project** and don't change its build action. - **Don't add it yourself and don't pass it on.** The package of your installation brings the license file that belongs to your license. The package `TXTextControl.TXSpell.Core.SDK`, for code without a user interface, brings a license file in the same way. [Package Overview](https://docs.textcontrol.com/tx-spell-dotnet-winforms/installation/nuget/packages/llms-full.txt) lists what the packages contain. ### .NET Framework Projects: licenses.licx In a .NET Framework project, the license is compiled into your assembly from the project's *licenses.licx* file, which lists the licensed classes. The file is in the *Properties* folder (C#) or the *My Project* folder (Visual Basic). The entry for the spell checker is: ```text TXTextControl.Proofing.TXSpellChecker, TXSpell.Windows.Forms ``` Code that uses the [TXSpell](https://docs.textcontrol.com/tx-spell-dotnet-winforms/reference/txtextcontrol-proofing/txspell/llms-full.txt) class without a user interface, for example together with a `ServerTextControl`, needs an entry for that class, with the version of the assembly: ```text TXTextControl.Proofing.TXSpell, TXSpell, Version=11.0.1000.500, Culture=neutral, PublicKeyToken=6b83fe9a75cfb638 ``` If the project has no *licenses.licx* yet, add a text file with this name and set its build action to **Embedded Resource**. The blog article [Using TX Spell .NET with ServerTextControl](https://www.textcontrol.com/blog/2016/04/26/using-tx-spell-net-with-servertextcontrol/) shows the entry for `TXSpell` for an earlier version. A project that uses TX Text Control as well has its entries in the same file. [Create a .NET Framework Application](https://docs.textcontrol.com/tx-spell-dotnet-winforms/getting-started/tx-text-control/dotnet-framework/llms-full.txt) shows the steps in a project. ### From the Trial to the Full Version > Warning > > **Trial Builds.** An application built with the trial version shows a dialog titled **TX Spell .NET Trial Version** every fifteen minutes. The trial may be used for evaluation and testing only, not in production or in an application you distribute. To switch to the full version: 1. Install the setup of the full version, *TX Spell .NET for Windows Forms 11.0 with SP1.exe*. 2. In a .NET project, install the TX Spell .NET package again from **Text Control Offline Packages**. In a .NET Framework project, reference the assemblies again from the *Assembly* folder of the installation. 3. Rebuild the application. The code doesn't change. ### Next Steps - [Application Licensing](https://docs.textcontrol.com/tx-spell-dotnet-winforms/installation/licensing/application/llms-full.txt): what your users need and what may ship with the application. - [Build Servers](https://docs.textcontrol.com/tx-spell-dotnet-winforms/installation/licensing/build-servers/llms-full.txt): licensing on build machines. - [Licensing](https://docs.textcontrol.com/tx-spell-dotnet-winforms/troubleshooting/licensing/llms-full.txt): the trial dialog and license entries in Troubleshooting. --- ## Nearby - **Previous:** [License Configuration](https://docs.textcontrol.com/tx-spell-dotnet-winforms/installation/licensing/llms-full.txt) - **Next:** [Application Licensing](https://docs.textcontrol.com/tx-spell-dotnet-winforms/installation/licensing/application/llms-full.txt)