TX Text Control .NET for WPF is a word processing control you place in a XAML window. It gives your application a complete editor — formatted text, paragraph and character styles, tables, images, headers and footers, footnotes, form fields and merge fields — and it reads and writes the formats your users already work in, including DOCX, DOC, RTF, HTML and PDF.

The same document engine is available without a user interface, so the documents your users edit on screen are the documents your code creates, merges and converts. Nothing else has to be installed on the machine: TX Text Control handles the formats itself, with no Microsoft Word and no Adobe Acrobat involved.

What It Gives Your Application

Your users get a word processor in a window, driven by ribbon tabs, toolbars, rulers, sidebars and a status bar, and your code gets the same documents without a user interface: it creates and converts them with ServerTextControl and fills templates with data through MailMerge. What You Can Build lists the tasks with the classes behind them.

Documents are loaded and saved through one set of stream types, so a file a user opens as DOCX can be saved as PDF, PDF/A, RTF, HTML or plain text without any other component. The ribbon tabs ship as WPF controls you place in your own ribbon, and the dialogs users expect — font, paragraph, tabs, tables, styles, images, hyperlinks, bookmarks, comments and tracked changes among them — are built in.

Who This Documentation Is for

It is written for .NET developers building WPF applications, and it assumes you know C# or Visual Basic, XAML and the WPF data binding model. It does not assume you know anything about TX Text Control.

How This Documentation Is Organized

Overview explains what the control is, how the editor and the engine relate, and what a document is made of.
Installation Guide covers the requirements, the packages and the licensing you need before you write any code.
Getting Started puts the control in a window and builds a working editor step by step.
The feature sections, Document Editor, Document Processing, Mail Merge and Reporting, PDF Processing and Digital Signatures, cover each feature in detail, in the editor and in code.
The application around the editor is the subject of the Integration Guide, with XAML, data binding and MVVM, and of the Deployment Guide, Security and Performance. What's New lists the changes of each version.
API Reference documents every class, property, method and event of the .NET API.

The .NET API

The .NET API divides the classes into namespaces: TXTextControl.WPF holds what belongs to WPF alone, such as the editing control and the ribbon tabs, TXTextControl the document engine and everything a document is made of, and TXTextControl.DocumentServer mail merge and reporting. Its overview lists every namespace with the classes to open first.

Where to Start

Overview: what the control does and how its parts fit together.
Installation Guide: what has to be in place first.
Getting Started: a working editor in a window.
TextControl: the class you will spend the most time in.

Getting Help

Something does not work. Troubleshooting collects common problems with the installation, the toolbox, licenses, native libraries, fonts, data binding and printing, and how to fix them.
You need working code. Examples lists the samples installed with the setup and the sample repositories of Text Control on GitHub, which receive new samples regularly, including samples that the setup doesn't install.
You need Text Control's support team. Registered users and developers who evaluate the trial version get free technical support. Open a ticket in the Support Center of your Text Control account; the support engineers answer in English and German. A subscription adds support by email, telephone and chat with no limit on the number of incidents, as described in Licensing.
You have a question about licenses or prices. Contact the Text Control sales team.