# Deployment

> Fix deployment problems of TX Spell .NET for Windows Forms: language data missing on the target machine, published applications and dialog languages.

- **Product:** TX Spell .NET for Windows Forms
- **Section:** Documentation
- **Kind:** Topic
- **Path:** TX Spell .NET for Windows Forms > Troubleshooting > Deployment
- **518 words**
- **Web URL:** https://docs.textcontrol.com/tx-spell-dotnet-winforms/troubleshooting/deployment/
- **LLMs URL:** https://docs.textcontrol.com/tx-spell-dotnet-winforms/troubleshooting/deployment/llms.txt
- **LLMs-Full URL:** https://docs.textcontrol.com/tx-spell-dotnet-winforms/troubleshooting/deployment/llms-full.txt

---

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](https://docs.textcontrol.com/tx-spell-dotnet-winforms/troubleshooting/dictionaries/llms-full.txt).

### 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:

```text
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, have to be shipped there. [Deploying .NET Framework Applications](https://docs.textcontrol.com/tx-spell-dotnet-winforms/deployment/dotnet-framework/llms-full.txt) lists the files and explains why the build output isn't enough.

### 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 together with TX Text Control, the application needs a target runtime. Publish to a folder, set the **Target runtime** to `win-x64` when the application uses TX Text Control, and deploy the complete content of the publish folder, as [Publishing .NET Applications](https://docs.textcontrol.com/tx-spell-dotnet-winforms/deployment/dotnet/llms-full.txt) shows.

### 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 and German, and the German texts are in the subfolder *de*, which has to be deployed. Other languages need a satellite assembly built with the Resource Kit, which is loaded only when the language of the system matches. [Localization and Resource Kit](https://docs.textcontrol.com/tx-spell-dotnet-winforms/user-interface/localization/llms-full.txt) shows how to deploy the German texts and build other languages.

### Related Pages

- [Deployment Guide](https://docs.textcontrol.com/tx-spell-dotnet-winforms/deployment/llms-full.txt): the files an application ships.
- [Dictionaries Not Found](https://docs.textcontrol.com/tx-spell-dotnet-winforms/troubleshooting/dictionaries/llms-full.txt): the messages about missing language data.
- [Licensing](https://docs.textcontrol.com/tx-spell-dotnet-winforms/troubleshooting/licensing/llms-full.txt): the license on the machines of your users.

---

## Nearby

- **Previous:** [Dictionaries Not Found](https://docs.textcontrol.com/tx-spell-dotnet-winforms/troubleshooting/dictionaries/llms-full.txt)
- **Next:** [Spell Checking](https://docs.textcontrol.com/tx-spell-dotnet-winforms/troubleshooting/spell-checking/llms-full.txt)