Redistribution Overview
What does a WPF application with TX Text Control take to the user's machine? The .NET assemblies of TX Text Control, including TXTextControl.WPF.dll with the controls your XAML uses, and the native libraries of the document engine in the bitness your application runs with. The user's machine adds the Microsoft Visual C++ runtime. No setup of TX Text Control runs there and no license file is copied, because the license is part of your compiled application.
What Ships
| Part | Files | Source |
|---|---|---|
| .NET assemblies | TXTextControl.WPF.dll, TXTextControl.dll, TXTextControl.Server.dll, TXDocumentServer.dll, TXDocumentServer.WPF.dll and the other assemblies of the engine | The NuGet package or the Assembly folder of the setup |
| Native libraries | A 32-bit or a 64-bit set, such as tx34.dll and the format filters tx34_dox.dll or tx34_pdf.dll | The runtimes folders of the NuGet package, or Assembly\bin and Assembly\bin64 of the setup |
| German resources | A de folder with TXTextControl.resources.dll and three more | The NuGet package |
Managed Assemblies and Native Libraries names every file, and 32-bit and 64-bit Applications explains why only one set of native libraries goes with each build.
All of these files go into the folder of your executable, as Where the Files Go explains.
What the User's Machine Needs
- The Microsoft Visual C++ runtime. The native libraries need VCRUNTIME140.DLL, installed with the Visual C++ Redistributable in the bitness of your application. See Visual C++ Runtime Dependencies.
- The Microsoft XML parser, if your application uses the XML features of TX Text Control. See The XML Parser.
- The .NET runtime or .NET Framework your application targets, unless a .NET application is published self-contained.
What Never Ships
The license file txtextcontrol.wpf.license, serial numbers, feed credentials and the NuGet package or the setup of TX Text Control stay out of every deployment. What Stays Out of the Installer lists them with the reasons, and Application Licensing has a checklist for a release build.
How the Files Reach the Deployment
| Project | What collects the files | Read |
|---|---|---|
.NET 8 or higher, with TXTextControl.TextControl.WPF.SDK | Publish in Visual Studio, or dotnet publish, with a target runtime | Publishing .NET Applications |
| .NET Framework 4.x, with the assemblies of the setup | You, from the Assembly folder of the installation | Deploying .NET Framework Applications |
The result is one folder. Deploy it with your own installer, as a file copy or as an MSIX package.
The Redistribution Rules
The license agreement allows royalty-free distribution of any number of compiled applications, with the runtime files that Text Control designates as redistributable, under conditions: for example, your application must offer substantial functionality beyond TX Text Control, and its recipients may not get your licensing information. Royalty-Free Distribution in the Licensing Overview lists all conditions, and Trial Version explains why a trial build must not be shipped.
Next Steps
- Managed Assemblies and Native Libraries: every file of the deployment.
- x86, x64, and AnyCPU: the native libraries each platform needs.
- Deployment: files that are missing on the user's machine.