Deployment Guide
Deploying an application with TX Spell .NET for Windows Forms means getting one folder onto the user's machine: your executable, TXSpell.dll and TXSpell.Windows.Forms.dll, and the four folders of language data the spell checker works with. No setup runs there, nothing is registered, and the license is already inside your assembly. The one thing that goes wrong is the language data, which your development machine finds in the installation and the user's machine doesn't.
The Deployment at a Glance
- One folder. Everything TX Spell .NET needs sits next to the executable: the assemblies, a de folder with the German dialog texts, and the folders Dictionaries, HyphenationLists, LanguageRecognition and SynonymLists.
- .NET 8 or higher: the NuGet package TXTextControl.TXSpell.WinForms.SDK copies these files, and Publish creates the folder.
- .NET Framework: you copy the files from the Assembly folder of the installation.
- Royalty-free: you may distribute any number of applications without runtime fees, under the conditions of the license agreement.
Find the Right Page
| If you want to | Read |
|---|---|
| Know what ships, what never ships, and what you may redistribute | Redistribution Overview |
| See every file of a deployment, or keep the language data in another folder | Assemblies and Language Data Folders |
| Publish a .NET 8 application with Visual Studio or the command line | Publishing .NET Applications |
| Deploy an application for the .NET Framework | Deploying .NET Framework Applications |
| Check the licensing side of a release | Application Licensing |
When spell checking works on your machine but not on the user's, see Deployment in the troubleshooting section. The deployment of TX Text Control, when your application uses it too, is described in the Deployment Guide of TX Text Control .NET for Windows Forms.