Managed Assemblies and Native Libraries

TX Text Control .NET for Windows Forms reaches your application as two kinds of files: .NET assemblies, which hold the classes your code uses, and native Windows libraries, which format, render, load and save the documents. The assemblies are the same for 32-bit and 64-bit applications; the native libraries exist once for each. Below is every file of version 34.0, where each one comes from and where it goes.

Managed Assemblies

The NuGet package TXTextControl.TextControl.WinForms.SDK 34.0.5 holds these assemblies in its lib/net8.0 folder. The Assembly folder of the setup holds the .NET Framework versions under the same names.

The requirements documentation lists all of these assemblies as files to deploy, so ship the complete set.

The package also contains TXTextControl.Windows.Forms.Design.dll, which Visual Studio's publish copies to the output like the others. The list of redistributable files in the requirements documentation doesn't name it.

Resources

A de subfolder of the package holds TXTextControl.resources.dll, TXDocumentServer.resources.dll, TXDrawing.resources.dll and TXBarcode.resources.dll: German versions of the built-in texts. Publishing copies them into a de folder next to the executable.

For other languages, you build satellite assemblies yourself with the Resource Kit of TX Text Control. Each goes into a subfolder named after its two-letter language code, such as fr, and each target machine needs a registry key under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\StrongName\Verification before the .NET Framework uses your own build. Localization and Resource Kit lists the keys and the steps.

Native Libraries

The native libraries format and render the documents and read and write the file formats, with one filter library per format family. Each set has the same thirteen files:

• 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

Your application loads the set that matches the bitness of its process. x86, x64, and AnyCPU explains which set each build configuration needs. The native libraries depend on the Microsoft Visual C++ runtime, which is installed on the user's machine rather than copied; see Visual C++ Runtime Dependencies.

The format filters have long carried the major version in their names, such as tx32_pdf.dll in version 32.0. Since version 33.0, the core libraries do as well: txkernel.dll, txtools.dll and txic.dll of version 32.0 became tx34.dll, tx34_tls.dll and tx34_ic.dll in version 34.0. The requirements documentation of TX Text Control still lists the old names, which the package of version 34.0 doesn't contain. Take the file names from the package, the publish folder or the Assembly\bin folders of your installation, and check them after every major version.

Where the Files Go

All files go into the folder of your application's executable, at the same level, except the de folder of the resources.

• Published with a target runtime, such as win-x64, a .NET application gets the native libraries of that runtime next to the executable.
• Built or published without a target runtime, the output holds both sets, in runtimes\win-x86\native and runtimes\win-x64\native.
• A .NET Framework application gets the native libraries only if you copy them from Assembly\bin or Assembly\bin64, as Deploying .NET Framework Applications describes.

Files That Aren't Deployed

The license file txtextcontrol.winforms.license, licenses.licx and the .nupkg file are used at build time only; the license is compiled into your assembly. Keep Licensing Information Out of the Deployment lists what must not ship.

Related Pages

• Redistribution Overview: what ships, what never ships and the redistribution rules.
• Package Overview: the NuGet package and its folders.
• Native Libraries and Architecture Mismatches: what to check when the native libraries don't load.
• Breaking Changes: file names that changed between versions.