Version 11.0 moves TX Spell .NET for WPF to .NET 8 and .NET 9 and delivers it as NuGet packages: one for WPF applications and one for .NET and ASP.NET Core applications without a user interface. It adds no classes or members to the API, so code written for version 10.0 keeps its calls.

Text Control released version 11.0 in March 2025, together with TX Text Control 33.0. It is the current version, and Service Pack 1 followed in April 2026; Service Packs has the dates and the package versions. The blog article The Wait is Over: TX Text Control for Linux is Officially Here announced TX Text Control 33.0 and lists TX Spell .NET 11.0 among the products released with it.

Version 11.0 at a Glance

Area	What is new
.NET	.NET 8 and .NET 9 applications, built in Visual Studio 2022
Packages	`TXTextControl.TXSpell.WPF.SDK` for WPF, `TXTextControl.TXSpell.Core.SDK` for .NET and ASP.NET Core
Deployment	The packages copy the language data into the build output, and publishing needs no manual steps
API	No new classes, properties, methods or events

.NET 8 and .NET 9

TX Spell .NET for WPF 11.0 supports .NET 8 and .NET 9, and you create the applications in Visual Studio 2022. Text Control names licensing and NuGet support among the parts adapted to .NET 9, and it states that version 11.0 was also prepared for the preview of .NET 10.

Both NuGet packages target net8.0. A project that uses them targets .NET 8 or higher: .NET 8 for a WPF App with the Long Term Support release, or a later version.

The NuGet Packages

The setup of TX Spell .NET for WPF adds the package source Text Control Offline Packages to NuGet, with two packages that target net8.0:

TXTextControl.TXSpell.WPF.SDK for WPF applications, with the TXSpellChecker component, its dialog boxes and its context menu.
TXTextControl.TXSpell.Core.SDK, new in this version, for .NET and ASP.NET Core applications without a user interface, with the TXSpell class; for example a server that checks the spelling in the Document Editor of TX Text Control .NET Server.

Besides the assemblies, both packages bring a license file and the US English language data, which the build copies into the output directory, so a new project checks, hyphenates and finds synonyms for English without further setup. Package Overview lists the contents of each package.

Publishing

TX Spell .NET 11.0 supports the Publish command of Visual Studio, and the NuGet packages copy the required files to the publish folder. When TX Spell .NET works together with TX Text Control, select a Target Runtime, such as win-x64, in the publish settings. Without TX Text Control, TX Spell .NET doesn't depend on a platform and is published without a target runtime.

Applications that don't use the NuGet packages are still deployed by hand: you copy the assemblies and the four folders from the \Assembly subdirectory of the TX Spell .NET installation directory into the folder of the application's executable.

Spell Checking in the Document Editor on Linux

With TXTextControl.TXSpell.Core.SDK, the Document Editor of TX Text Control .NET Server checks spelling in an ASP.NET Core application that runs in a Linux container. The blog article Document Editor with TX Spell .NET on Linux using ASP.NET Core sets up such an application with .NET 10 and the packages of TX Text Control 34.0.

Next Steps

Service Packs: the release dates and package versions of Service Pack 1.
Breaking Changes: what an upgrade from version 10.0 needs, such as the change to .NET 8.
Version 10.0: the features of the previous version.
Getting Started: connect the spell checker to a control and check a first text.

What's New in TX Spell .NET for WPF 11.0