TX Text Control .NET for WPF

What's New in TX Text Control .NET for WPF 34.0

Topic

Every PDF document that TX Text Control .NET for WPF 34.0 saves is tagged for accessibility, and new properties and ribbon items give its elements the descriptive texts that screen readers need. What follows lists the features, classes, properties and events the version added since 33.0, each linked to the reference member or the page that describes it.

Version 34.0 was released in November 2025 and is the current major version. Text Control released TX Text Control .NET Server, TX Text Control .NET for Windows Forms and TX Text Control ActiveX 34.0 at the same time. Service Pack 5, released on September 14, 2026, is its latest update; Service Packs lists all of them.

Version 34.0 at a Glance

AreaWhat is new
PDFTagged PDF documents for PDF/UA and PDF/A-3a, descriptive texts for links, form fields, tables and frames
RibbonItems to enter the descriptive text of form fields, frames and tables, and a new table properties group
Mail mergeThe FrameMergedEventArgs base class and the descriptive text of merged images
.NET.NET 8, .NET 9 and .NET 10, Visual Studio 2022 and Visual Studio 2026

PDF Accessibility and Archiving

Version 34.0 changes the structure of the PDF documents that TX Text Control writes. Your existing code produces the new structure without changes. What TX Text Control can't produce on its own are the descriptive texts of your content, and version 34.0 adds the properties to set them.

  • Tagged PDF. A PDF document now contains a logical structure in addition to its visible content, stored apart from it, so the order of its elements doesn't depend on where the objects are placed on the page.
  • PDF/UA by default. PDF documents contain the tags and metadata that PDF/UA, the standard for documents read with assistive technologies, requires. Whether a document fully complies depends on its content: an image without a descriptive text, for example, can't be read aloud.
  • PDF/A-3a. StreamType.AdobePDFA writes PDF/A-3a instead of PDF/A-1b. See PDF/A.
  • Descriptive texts. Five new DescriptiveText properties, of HypertextLink, DocumentLink, FormField, Table and FrameBase, describe elements that a screen reader can't read from the text itself. FrameBase covers every frame: images, text frames, signature fields, charts, barcodes and drawings. An empty string means that the element has no descriptive text.

Create an Accessible PDF (PDF/UA) shows which property describes which element, with code that checks a document before it's saved. The blog article PDF/UA vs. PDF/A-3a: Which Format Should You Use for Your Business Application? compares the two standards.

Descriptive Texts in the Ribbon

Users set descriptive texts in the ribbon as well. Version 34.0 adds these values to the RibbonItem enumerations of three ribbon tabs, which identify the new items:

Ribbon tabNew items
RibbonFormFieldsTabTXITEM_FormFieldDescriptiveText, with its image TXITEM_FormFieldDescriptiveText_Image, see RibbonFormFieldsTab.RibbonItem
RibbonFrameLayoutTabTXITEM_ObjectDescriptiveText, with TXITEM_ObjectDescriptiveText_Image and TXITEM_ObjectDescriptiveText_TextBox, for images, text frames, drawings and barcodes, see RibbonFrameLayoutTab.RibbonItem
RibbonTableLayoutTabThe new group TXITEM_TablePropertiesGroup with TXITEM_TableID and TXITEM_TableDescriptiveText, each with an _Image and a _TextBox item, see RibbonTableLayoutTab.RibbonItem

The identifiers also name the resources of each item, such as its icon and text; the _Image items name only the icon. If your application changes the ribbon tabs in code, check it against the new items. Built-in Ribbon Tabs describes the tabs.

Mail Merge

MailMerge creates documents from a template and data. It raises events when it has merged a barcode, a chart or an image, and version 34.0 extends the arguments of these events.

FrameMergedEventArgs provides these properties:

PropertyReturns
FrameThe frame that has been merged
DataRowThe data row that supplied the frame with merge content
MergeBlockNameThe name of the merge block, a section of the template that is repeated for each record, if the frame is part of one
NestingDepthThe one-based nesting depth of that merge block
SubTextPartIDThe ID of the SubTextPart, a user-defined part of the document, that contains the frame, or 0
SubTextPartNumberThe one-based number of that subtext part, or 0

Merge Events covers the events of a mail merge.

.NET and Visual Studio

  • .NET 10. The package TXTextControl.TextControl.WPF.SDK targets .NET 8 and supports .NET 8, .NET 9 and .NET 10. Text Control tested version 34.0 with WPF applications on .NET 10, and existing code runs on it without changes. See .NET and .NET Framework.
  • Visual Studio 2026. Version 34.0 supports Visual Studio 2022 and Visual Studio 2026. Text Control tested the NuGet package and the Visual Studio tooling, including the toolbox and the designers, in Visual Studio 2026. See Visual Studio.

The blog article Day-1 Support for .NET 10 in TX Text Control 34.0 describes the tests.

New Classes and Members

The What's New documentation of version 34.0 lists these classes and properties as new in TX Text Control .NET for WPF, grouped by class. Each name leads to its reference page.

The list of the documentation also names the HypertextLink class and its Target property, the target a hypertext link points to. Both existed before version 34.0; of HypertextLink, only DescriptiveText is new.

Upgrade to Version 34.0

Version 34.0 changes no existing API, and its package targets .NET 8, like the 33.0 package. Test the PDF output of your application, which is now tagged. Breaking Changes in the Upgrade Guide lists what to check, and Upgrading from Previous Versions has the steps.

Next Steps

  • Version 33.0: the features of the previous version.
  • Breaking Changes: the changes that can require work when you upgrade.
  • Service Packs: the service packs of version 34.0.
  • Introducing TX Text Control 34.0: Your Next Leap in Document Processing: the release announcement on the Text Control Blog.