Redistribution Overview
An application with TX Spell .NET for WPF takes three things to the user's machine: the two assemblies of TX Spell .NET, the language data it checks with, and nothing else. There is no setup to run, no runtime to register and no license file to copy, and you may distribute the application royalty-free. What needs care is completeness: the language data folders, which the spell checker finds on your development machine without being copied, have to reach the user too.
What Ships
| Part | Files | Where it goes |
|---|---|---|
| Assemblies | TXSpell.dll and TXSpell.WPF.dll | Next to the executable |
| Dialog texts in German | de\TXSpell.resources.dll | A de folder next to the executable |
| Language data | The folders Dictionaries, HyphenationLists, LanguageRecognition and SynonymLists | Next to the executable |
The packages and the setup contain managed assemblies only, so nothing has to be installed on the user's machine besides .NET or the .NET Framework. TX Spell .NET uses every file in the four language data folders automatically, so the languages you ship are the languages it checks. Assemblies and Language Data Folders lists every file.
What Never Ships
- The license file. The license is compiled into your assembly when you build, so the published folder contains none; see Application Licensing.
- Licensing information of any kind: serial numbers, license keys, credentials, or a nuget.config file with the token of the private feed.
- The NuGet packages and the setup. The user's machine needs the files your application runs with, not the packages they came in. The packages may not be republished or repackaged for others.
Two Ways to Deploy
| Your application | How the files get there | Read |
|---|---|---|
| .NET 8 or higher, with the NuGet package | Publish in Visual Studio or dotnet publish copies everything into the publish folder | Publishing .NET Applications |
| .NET Framework, with the setup | You copy the files from the Assembly folder of the installation | Deploying .NET Framework Applications |
Either way, the result is one folder that you deploy as a whole, with your installer, a file copy or any other tool.
Your Right to Redistribute
You may distribute any number of compiled applications with the runtime files of TX Spell .NET royalty-free, to customers, to third parties and to users within your organization, under the conditions that Application Licensing lists.
Dictionaries and Their Licenses
The license agreement places the dictionaries in the Dictionaries folder of TX Spell .NET under the LGPL: they may be redistributed freely as long as they are unmodified. Each dictionary also comes with license files of its own, such as README_en_US.txt next to the US English dictionary; ship them with it, and follow them. Dictionaries, hyphenation lists and thesaurus files you download carry their own licenses, which differ from language to language; Hunspell and OpenOffice Dictionaries explains what to check.
Next Steps
- Assemblies and Language Data Folders: every file of a deployment, and custom folder locations.
- Publishing .NET Applications: publish with Visual Studio or the command line.
- Deployment: what to do when spell checking works on your machine only.