Deployment
An application that checks spelling on your development machine can fail on the machine of a user, because TX Spell .NET finds its language data in the installation directory on your machine but only next to the application elsewhere. The problems below start from how the application was deployed. The messages about missing folders are explained on Dictionaries Not Found.
Spell Checking Works on Your Machine Only
On the target machine, TX Spell .NET reports that a folder of its language data is missing, for example:
Neither a Dictionaries directory was found inside the application's executable program file folder, nor a valid TXSpell registry key referring to the corresponding default directory could be detected.
On a development machine, TX Spell .NET finds the language data in the \Assembly subdirectory of its installation. On any other machine, it looks only in the folder of the application's executable, so the assemblies and the four language data folders, with the dictionaries you added for other languages, must be copied there, into the Bin folder in an ASP.NET application. Deploying .NET Framework Applications lists what to copy, and Assemblies and Language Data Folders every file.
A Published Application Misses Files
An application that you published with Visual Studio fails on the target machine.
The NuGet packages copy the required files, including the four folders, into the publish folder, but the complete folder must be deployed, and together with TX Text Control, the application needs the target runtime win-x64. Without TX Text Control, TX Spell .NET needs no target runtime. Publish again as Publish With Visual Studio describes, and deploy the complete content of the publish folder.
The Dialogs Aren't in the User's Language
The spell check dialog and the options dialog are shown in English on a machine with another language.
The texts of the dialogs are built in for English, the packages bring the German texts in the subfolder de, and a satellite assembly for another language, built with the Resource Kit, is loaded only when the language of the system matches. Deploy the de folder with TXSpell.resources.dll for German, and for another language the satellite assembly in a folder named with its two-letter code, such as fr. Localization and Resource Kit describes the Resource Kit, which was written for the .NET Framework.