Redistribution Overview
Before a Windows Forms application built with TX Text Control goes to its users, you decide which files travel with it. The answer is short: the .NET assemblies of TX Text Control, the native libraries for the bitness of your application and, on the user's machine, the Microsoft Visual C++ runtime. No setup of TX Text Control runs there, nothing is registered, and the license is already compiled into your application.
What Ships
| Part | Files | Where they come from |
|---|---|---|
| .NET assemblies | TXTextControl.dll, TXTextControl.Windows.Forms.dll, TXTextControl.Server.dll, TXDocumentServer.dll and the other assemblies of the engine | The NuGet package or the Assembly folder of the setup |
| Native libraries | One set for 32-bit and one for 64-bit processes, such as tx34.dll and the format filters tx34_rtf.dll or tx34_pdf.dll | The runtimes folders of the NuGet package, or Assembly\bin and Assembly\bin64 of the setup |
| German resources | TXTextControl.resources.dll and three more in a de folder | The NuGet package |
Your application ships the native libraries of the bitness it runs with, not both sets. 32-bit and 64-bit Applications explains why, and Managed Assemblies and Native Libraries lists every file.
All files of TX Text Control go into the application's folder, at the same level as the executable, as Put All Files Into the Application Folder shows.
What the User's Machine Needs
- The Microsoft Visual C++ runtime. The native libraries use VCRUNTIME140.DLL. Install the Visual C++ Redistributable of the same bitness as your application; see Visual C++ Runtime Dependencies.
- The Microsoft XML parser for the XML features of TX Text Control, as Other Windows Components describes.
- .NET or the .NET Framework that your application targets, unless you publish a .NET application as self-contained.
What Never Ships
The license is compiled into your application, so the license file, serial numbers, license keys, your nuget.config with its API token and the NuGet package or setup of TX Text Control stay behind. Keep Licensing Information Out of the Deployment lists them and shows where they can slip in.
Two Ways to Deploy
| Your project | How the files reach the output | Read |
|---|---|---|
.NET 8 or higher, with TXTextControl.TextControl.WinForms.SDK | Publish in Visual Studio or dotnet publish with a target runtime copies all files into one folder | Publishing .NET Applications |
| .NET Framework 4.x, with the assemblies of the setup | You copy the files from the Assembly folder of the installation | Deploying .NET Framework Applications |
Either way, the result is one folder that you deploy as a whole: with your own installer, as an MSIX package or as a file copy.
Your Right to Redistribute
TX Text Control .NET for Windows Forms is royalty-free: you may distribute any number of compiled applications with the runtime files listed above, without runtime fees, as long as your application adds substantial functionality and doesn't pass TX Text Control on as a library of its own. Royalty-Free Distribution lists all conditions of the license agreement, and Trial Version and Express Edition explains why a trial build must not be distributed.
Next Steps
- Managed Assemblies and Native Libraries: every file and what it does.
- Publishing .NET Applications: publish a .NET 8 or higher application with its files.
- Deployment: what to check when files are missing on the user's machine.