TX Text Control .NET for Windows Forms is a word processing component you drop onto a form. 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

A TextControl gives your users a word processor on a form. The ribbon, toolbars, rulers, sidebar and status bar around it drive the editor, ServerTextControl processes documents with no user interface at all, and MailMerge builds invoices, letters and reports from a template and your data. What You Can Build matches these classes to typical tasks.

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 dialogs users expect — font, paragraph, tabs, tables, styles, images, hyperlinks, bookmarks, comments and tracked changes among them — are built in and can be opened from your own menus.

Who This Documentation Is for

It is written for .NET developers building Windows desktop applications, and it assumes you know C# or Visual Basic and Windows Forms. It does not assume you know anything about TX Text Control.

How This Documentation Is Organized

Overview explains what the component 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 component on a form 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 the designer, user controls, databases and menus, 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 documents every class, property, method and event. Its main namespaces are TXTextControl for the editor, the engine and the elements of a document, TXTextControl.DocumentServer for mail merge and reporting, and TXTextControl.Windows.Forms for the ribbon and the sidebar; the Introduction describes what each one holds.

Where to Start

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

Getting Help

Something does not work. Troubleshooting collects common problems and their fixes.
You need working code. Examples lists the TX Words sample applications, the samples of the setup and the repositories of Text Control on GitHub, which receive new samples regularly.
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 direct access to the support engineers with an unlimited number of incidents for one year, as described in Subscription and Updates.
You have a question about licenses or prices. Contact the Text Control sales team.