Deployment Guide
Your Windows Forms application runs on your development machine; the Deployment Guide gets it running on the machines of your users. It covers the files of TX Text Control that go with your application, the Visual C++ runtime they need, the choice between x86, x64 and AnyCPU, publishing .NET and .NET Framework applications, the license in a deployed application, MSIX packages and build pipelines.
The Deployment at a Glance
- One folder. Your executable, the .NET assemblies of TX Text Control and the native libraries of one platform, all at the same level.
- One bitness. The native libraries exist for 32-bit and for 64-bit processes, and your application ships the set it runs with.
- One runtime to install. The native libraries need the Microsoft Visual C++ runtime, VCRUNTIME140.DLL, on the user's machine.
- No license file. The license is compiled into your application when you build it. Users need no serial number, no activation and no runtime license, and you pay no royalties.
How the files reach the folder depends on the project: a .NET 8 or higher project publishes them from the NuGet package TXTextControl.TextControl.WinForms.SDK, and a .NET Framework project copies them from the installation folder of the setup.
Find the Right Page
| If you want to | Read |
|---|---|
| Know which files ship and what you may redistribute | Redistribution Overview |
| See every assembly and native library of version 34.0 | Managed Assemblies and Native Libraries |
| Install the Visual C++ runtime on the user's machine | Visual C++ Runtime Dependencies |
| Decide between x86, x64 and AnyCPU | x86, x64, and AnyCPU |
| Publish a .NET 8 or higher application | Publishing .NET Applications |
| Deploy a .NET Framework application, or use ClickOnce | Deploying .NET Framework Applications |
| Check the license of a release build | Application Licensing |
| Package the application as MSIX | MSIX Packaging and Microsoft Store Deployment |
| Build and publish on a build server | CI/CD |
Where to Start
- Read Redistribution Overview to see what a deployment contains.
- Choose the platform in x86, x64, and AnyCPU.
- Follow Publishing .NET Applications or Deploying .NET Framework Applications, depending on your project.
- Before the release, go through Application Licensing.
When the application fails on the user's machine, Deployment and Native Libraries and Architecture Mismatches in the Troubleshooting section list the usual causes. If your application also checks spelling with TX Spell .NET, its files are described in the Deployment Guide of TX Spell .NET for Windows Forms.
Pages in This Section
- Redistribution Overview: what ships, what never ships and the redistribution rules of the license agreement.
- Managed Assemblies and Native Libraries: every file of TX Text Control and where it goes.
- Visual C++ Runtime Dependencies: the runtime of the native libraries and the XML parser.
- x86, x64, and AnyCPU: the native libraries each build configuration needs.
- Publishing .NET Applications: publish with Visual Studio or
dotnet publishfor a target runtime. - Deploying .NET Framework Applications: copy the files of the setup, and deploy with ClickOnce.
- Application Licensing: the license in a deployed application, and what must not ship.
- MSIX Packaging and Microsoft Store Deployment: package, sign and sideload, and run in an AppContainer.
- CI/CD: build and publish with GitHub Actions and Azure Pipelines.