# Deploying .NET Framework Applications

> Deploy a .NET Framework WPF app with TX Spell .NET: copy TXSpell.WPF.dll and the language data from the Assembly folder, and why the build output falls short.

- **Product:** TX Spell .NET for WPF
- **Section:** Documentation
- **Kind:** Topic
- **Path:** TX Spell .NET for WPF > Deployment Guide > Deploying .NET Framework Applications
- **811 words**
- **Web URL:** https://docs.textcontrol.com/tx-spell-dotnet-wpf/deployment/dotnet-framework/
- **LLMs URL:** https://docs.textcontrol.com/tx-spell-dotnet-wpf/deployment/dotnet-framework/llms.txt
- **LLMs-Full URL:** https://docs.textcontrol.com/tx-spell-dotnet-wpf/deployment/dotnet-framework/llms-full.txt

---

A WPF application for the .NET Framework is deployed by copying files: the application's executable, the assemblies of TX Spell .NET and the language data, all in one folder on the user's machine. No NuGet package does this for you, and one thing is easy to miss: the language data, which the application finds on your development machine without being copied, has to be shipped.

### What Goes Next to the Executable

Copy these files and folders into the folder of the application's executable. They come from the *Assembly* folder of the TX Spell .NET installation:

```text
MyApp.exe
TXSpell.dll
TXSpell.WPF.dll
de\
Dictionaries\
HyphenationLists\
LanguageRecognition\
SynonymLists\
```

Ship the *de* folder when the dialogs should appear in German. Every file in the four language data folders is used automatically.

![The Select the files to reference dialog of Visual Studio showing the Assembly folder of an earlier TX Spell .NET installation, with the folders de, Dictionaries, HyphenationLists, LanguageRecognition and SynonymLists and the files TXSpell.dll and TXSpell.WPF.dll.](https://docs.textcontrol.com/assets/img/tx-spell-dotnet-wpf/vs-reference-assemblies.c77d9f26.webp)

[Assemblies and Language Data Folders](https://docs.textcontrol.com/tx-spell-dotnet-wpf/deployment/assemblies/llms-full.txt) lists every file, and [Installing Dictionaries and Language Data](https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/language-data/llms-full.txt) explains the folders.

### Why the Build Output Isn't Enough

> Warning
>
> **Works on Your Machine Only.** On your development machine, the spell checker finds the language data below the *Assembly* folder of the installation, even when the output folder of your project has none. The machines of your users have no installation, so there it looks only in the folder of the application; [Where the Spell Checker Looks](https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/language-data/#where-the-spell-checker-looks) explains the default and how to use another folder.

Test the deployed application on a machine without TX Spell .NET, or copy the folders into your output folder during the build, so that you see what your users see.

### ASP.NET Applications

An ASP.NET application for the .NET Framework that checks text with the [TXSpell](https://docs.textcontrol.com/tx-spell-dotnet-wpf/reference/txtextcontrol-proofing/txspell/llms-full.txt) class, such as the Web Forms sample on [GitHub Examples](https://docs.textcontrol.com/tx-spell-dotnet-wpf/examples/github/llms-full.txt), has no folder of an executable. There, *TXSpell.dll* and the four language data folders go into the *Bin* folder of the application instead.

### Framework Versions

TX Spell .NET for WPF requires the .NET Framework 4.5 or higher on the user's machine. [.NET and .NET Framework](https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/requirements/dotnet/llms-full.txt) lists the versions.

### The License Is Already Inside

In a .NET Framework project, the license is compiled into your assembly from *licenses.licx* when you build, so there is no license file to ship and nothing to install on the user's machine; [.NET Framework Projects: licenses.licx](https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/licensing/development/#net-framework-projects-licenses-licx) shows the entry. Build the application with the full version of TX Spell .NET, and see [Application Licensing](https://docs.textcontrol.com/tx-spell-dotnet-wpf/deployment/licensing/llms-full.txt) for the checklist before a release.

### After a Service Pack

A service pack keeps the assembly version, 11.0.1000.500. Install it on the development machine, rebuild the application, and ship the new assemblies from the *Assembly* folder with the next release.

### With TX Text Control

An application that uses TX Text Control as well ships its files too: the assemblies and native libraries of TX Text Control, which its Deployment Guide lists in [Deploying .NET Framework Applications](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/deployment/dotnet-framework/llms-full.txt). The licenses of both products are compiled from the same *licenses.licx*.

### Next Steps

- [Assemblies and Language Data Folders](https://docs.textcontrol.com/tx-spell-dotnet-wpf/deployment/assemblies/llms-full.txt): every file, and where it comes from.
- [Application Licensing](https://docs.textcontrol.com/tx-spell-dotnet-wpf/deployment/licensing/llms-full.txt): what to check before you ship.
- [Deployment](https://docs.textcontrol.com/tx-spell-dotnet-wpf/troubleshooting/deployment/llms-full.txt): when the deployed application doesn't find its files.

---

## Nearby

- **Previous:** [Publishing .NET Applications](https://docs.textcontrol.com/tx-spell-dotnet-wpf/deployment/dotnet/llms-full.txt)
- **Next:** [Application Licensing](https://docs.textcontrol.com/tx-spell-dotnet-wpf/deployment/licensing/llms-full.txt)