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 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 describes.

The conditions of royalty-free distribution are on Application Licensing 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 describes what a renewal adds.

With TX Text Control

TX Text Control is licensed separately, with its own license agreement and deployment licensing. 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: royalty-free distribution and its conditions.
Build Servers: licensed builds on build machines.
Redistribution Overview: the files that ship with your application.