Deployment Guide
Deploying a WPF application with TX Text Control means bringing a small, fixed set of files to the user's machine and one runtime that Windows may lack. The Deployment Guide of TX Text Control .NET for WPF names those files, explains the choice of platform, shows how to publish .NET and .NET Framework applications, package them as MSIX and build them in a pipeline, and checks the license of a release build.
What a Deployment Looks Like
| Files of TX Text Control | The .NET assemblies, such as TXTextControl.WPF.dll, and the native libraries of one bitness, such as tx34.dll |
| Where they go | Into the folder of your executable, at the same level |
| Where they come from | The NuGet package TXTextControl.TextControl.WPF.SDK for .NET 8 or higher, the Assembly folder of the setup for the .NET Framework |
| What the machine needs | The Microsoft Visual C++ runtime in the bitness of your application, and the .NET runtime your application targets |
| License | Compiled into your application; nothing to install, activate or pay for per user |
Find the Right Page
| If you want to | Read |
|---|---|
| Know what ships, what doesn't and what the license agreement allows | Redistribution Overview |
| Look up every assembly and native library | Managed Assemblies and Native Libraries |
| Provide the Visual C++ runtime | Visual C++ Runtime Dependencies |
| Choose between x86, x64 and AnyCPU | x86, x64, and AnyCPU |
| Publish a WPF application for .NET 8 or higher | Publishing .NET Applications |
| Deploy a WPF application for the .NET Framework, also with ClickOnce | Deploying .NET Framework Applications |
| Make sure a release build is licensed correctly | Application Licensing |
| Create an MSIX package or run in an AppContainer | MSIX Packaging and Microsoft Store Deployment |
| Publish from GitHub Actions or Azure Pipelines | CI/CD |
Recommended Order
- Redistribution Overview gives you the complete picture.
- x86, x64, and AnyCPU settles the platform, which decides the native libraries.
- Publishing .NET Applications or Deploying .NET Framework Applications produces the folder you deploy.
- Application Licensing is the check before the release.
Problems on the user's machine are covered in the Troubleshooting section, on Deployment and Native Libraries and Architecture Mismatches. For TX Spell .NET in the same application, see the Deployment Guide of TX Spell .NET for WPF.
Pages in This Section
- Redistribution Overview — the files that ship, the files that never ship and the redistribution rules.
- Managed Assemblies and Native Libraries — every file of version 34.0 and its place in the application folder.
- Visual C++ Runtime Dependencies — VCRUNTIME140.DLL, its redistributable and the XML parser.
- x86, x64, and AnyCPU — the native libraries of each platform, in .NET and .NET Framework projects.
- Publishing .NET Applications — Visual Studio and
dotnet publishwith a target runtime. - Deploying .NET Framework Applications — the folders of the setup, and ClickOnce.
- Application Licensing — the license in the deployed application and a checklist for releases.
- MSIX Packaging and Microsoft Store Deployment — packaging project, signing, sideloading and AppContainers.
- CI/CD — a GitHub Actions workflow that publishes an artifact, and Azure Pipelines.