.NET Versions
Which .NET version can a project with TX Text Control .NET Server 34.0 target? The supported .NET versions and the target frameworks of the NuGet packages answer that question when you create a project, choose a target framework or plan to move an existing .NET Framework application.
Supported .NET Versions
The NuGet packages of TX Text Control .NET Server 34.0 support the following .NET versions:
| .NET version | Release type | Support in TX Text Control .NET Server 34.0 |
|---|---|---|
| .NET 10 | Long Term Support (LTS) | Supported since the release of version 34.0. The current tutorials use .NET 10. |
| .NET 9 | Standard Term Support (STS) | Supported |
| .NET 8 | Long Term Support (LTS) | Supported. This is the minimum version. |
The packages of the Core and Classic engines require .NET 8 or higher. Every package contains assemblies compiled for .NET 8 (target framework net8.0), so you can use them in projects that target .NET 8, .NET 9 or .NET 10. Text Control tested version 34.0 with .NET 10, including ASP.NET Core and Blazor applications, Azure applications, and the NuGet packages and tooling in Visual Studio 2026. Existing TX Text Control code runs on .NET 10 without code changes.
Microsoft ends support for each .NET version on a fixed date. Check the .NET and .NET Core official support policy when you choose the version for a new project.
Target Frameworks of the NuGet Packages
| Package | Target frameworks |
|---|---|
TXTextControl.TextControl.Core.SDK | net8.0 |
TXTextControl.TextControl.ASP.SDK | net8.0 |
TXTextControl.Web.DocumentEditor.Backend | net8.0 |
TXTextControl.Web.Blazor.DocumentEditor | net8.0 |
TXTextControl.Web | net8.0 and .NET Framework 4.5 |
TXTextControl.Web.DocumentViewer | net8.0 and .NET Framework 4.5 |
TXTextControl.Web.DocumentViewer.Classic | net8.0 and .NET Framework 4.5 |
The engine packages TXTextControl.TextControl.Core.SDK and TXTextControl.TextControl.ASP.SDK have no .NET Framework build. The .NET Framework builds of the three web packages depend on ASP.NET MVC 5 (Microsoft.AspNet.Mvc). For all packages and what they contain, see Package Overview.
.NET Framework for Classic ASP.NET Applications
The Classic engine is also available for ASP.NET applications on the .NET Framework, such as ASP.NET MVC and Web Forms applications. These applications run on Windows only and get the TX Text Control files from the Windows setup instead of the engine NuGet packages.
The requirements for ASP.NET applications on the .NET Framework list the following versions:
- .NET Framework 4.0
- .NET Framework 4.5
- .NET Framework 4.6
- .NET Framework 4.7
- .NET Framework 4.8
The Core engine and Linux support are not available for .NET Framework applications. If you plan to move an existing application to .NET 8 or higher, use one of the engine NuGet packages: TXTextControl.TextControl.Core.SDK for Windows and Linux, or TXTextControl.TextControl.ASP.SDK if the application stays on Windows and needs the Classic engine. See Migrating from Previous Versions.
Choosing a Version
- New projects: The Getting Started tutorials use Visual Studio 2026 and .NET 10 (Long Term Support). Any version from .NET 8 works with the same packages.
- Existing .NET 8 or .NET 9 projects: You do not need to change the target framework to use version 34.0.
- Updating an application to .NET 10: Change the target framework of your project. The TX Text Control APIs stay the same.
- .NET Framework applications: To use the engine NuGet packages, the Core engine or Linux, the application must target .NET 8 or higher.
Next Steps
- Operating Systems — where you can develop and deploy with each engine.
- Development Environments — Visual Studio, Visual Studio Code, the .NET CLI and the tools for Angular and React.
- Package Overview — which NuGet package you need for which task.
- Migrating from Previous Versions — moving from the .NET Framework and older versions.