Managed Assemblies and Native Libraries

Every file of TX Text Control .NET for WPF that your application deploys is one of two kinds. The .NET assemblies hold the classes: the WPF controls your XAML maps with clr-namespace:TXTextControl.WPF;assembly=TXTextControl.WPF, ServerTextControl, mail merge and the rest of the engine. The native libraries do the document work, and they come in a 32-bit and a 64-bit set. The lists below are those of version 34.0 and the package TXTextControl.TextControl.WPF.SDK 34.0.5.

Managed Assemblies

The package holds the assemblies in lib/net8.0; the setup installs the .NET Framework versions under the same names in its Assembly folder.

The requirements documentation lists these assemblies together as the files to deploy; ship all of them. Unlike the Windows Forms package, the WPF package has no separate design-time assembly.

Resources

The de folder of the package holds German resources of TXTextControl.dll, TXDocumentServer.dll, TXBarcode.dll and TXDrawing.dll, one .resources.dll file each. A publish copies them into a de folder next to the executable.

Satellite assemblies for other languages are built with the Resource Kit of TX Text Control and deployed in a subfolder named after the two-letter language code, such as fr. The .NET Framework uses such a build of your own only if each target machine has a registry key under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\StrongName\Verification; Localization and Resource Kit lists the keys and the steps.

Native Libraries

The native libraries format and render documents and read and write the file formats, one filter library per format family. A set consists of these thirteen files, in 32-bit and in 64-bit versions of the same names:

• tx34.dll, tx34_ic.dll and tx34_tls.dll
• tx34_rtf.dll, tx34_htm.dll, tx34_doc.dll, tx34_dox.dll, tx34_xml.dll, tx34_css.dll, tx34_xlx.dll and tx34_pdf.dll
• txsvggen.dll and txdomprs.dll

A process loads the set of its own bitness, so each build deploys one set; x86, x64, and AnyCPU says which. The libraries rely on the Microsoft Visual C++ runtime, which is installed on the user's machine, not copied: see Visual C++ Runtime Dependencies.

The format filters carry the major version in their names, as tx34_pdf.dll does now and tx32_pdf.dll did in version 32.0. The core libraries got it in version 33.0: tx34.dll, tx34_tls.dll and tx34_ic.dll take the place of the txkernel.dll, txtools.dll and txic.dll of version 32.0. The requirements documentation still names these three old files, which the 34.0 package doesn't contain. An installer with a file list takes the names from the package, the publish folder or the Assembly\bin folders, and needs a new list with each major version.

Where the Files Go

Everything goes into the application's root folder, at the same level as the executable, with the German resources in their de folder. An application installed as C:\Program Files\My Application\My Application.exe has all files of TX Text Control in C:\Program Files\My Application.

• A .NET publish with a target runtime, such as win-x64, places the native libraries of that runtime next to the executable.
• A build or publish without a target runtime keeps both sets in runtimes\win-x86\native and runtimes\win-x64\native.
• A .NET Framework application has native libraries only after you copy them from Assembly\bin or Assembly\bin64; see Deploying .NET Framework Applications.

Files That Stay Behind

Some files of a project with TX Text Control are used only by the build: the license file, licenses.licx and the NuGet package. What Stays Out of the Installer lists them with everything else that must not be deployed.

Related Pages

• Redistribution Overview: what ships and the redistribution rules.
• Assemblies and XAML Namespaces: the assemblies from the view of your XAML.
• Native Libraries and Architecture Mismatches: when the native libraries don't load.
• Breaking Changes: file names that changed between versions.