Installation Guide
Before <WPF:TextControl /> shows an editor in the XAML Designer, a few things have to be in place on the development machine: a supported Windows and Visual Studio, the setup of TX Text Control .NET for WPF 34.0, the NuGet package or the assembly references in the project and a license that reaches the build. The Installation Guide goes through each of them in order and comes back later when a service pack or a new version is due.
If you would rather start with a working window, go to Getting Started; its tutorials link back here for the details.
How You Get the Product
| Development machine | Build server or CI/CD pipeline | |
|---|---|---|
| What you install | The setup of the full or the trial version | Nothing but the NuGet package |
| .NET 8 or higher projects | TXTextControl.TextControl.WPF.SDK from the local package source Text Control Offline Packages | TXTextControl.TextControl.WPF.SDK from the Text Control Private NuGet Feed |
| Visual Studio toolbox and XAML Designer | Provided by the setup and the package | Not needed |
The setup is where every development machine starts: it brings the offline package source, the assemblies for .NET Framework projects, the toolbox items and the samples. The package from the private feed compiles projects but contains no design-time components. Installing the Product describes both setups and what they install.
The Installation Path
- Check the requirements. You develop on Windows 10, Windows 11 or Windows Server with Visual Studio. The package targets .NET 8 or higher, and the setup also supports the .NET Framework 4.x. See System Requirements.
- Install the product. Run the setup of the full or the trial version. See Installing the Product.
- Add the package to .NET projects. Install
TXTextControl.TextControl.WPF.SDK, which contains the WPF controls, the document engine and the license. See NuGet Packages. - Place the controls. Add the editor, its bars and ribbon tabs from the toolbox and connect them by name. See Visual Studio Toolbox and XAML Designer.
- Know the namespaces. Read the
xmlnsdeclaration Visual Studio writes, and find the assembly of each class. See Assemblies and XAML Namespaces. - Check your licenses. Every developer needs an assigned license, and the build compiles it into your application, which you distribute royalty-free. See License Configuration.
- Stay current. Install service packs, update the package in your projects and check the breaking changes of a new version. See Upgrade Guide.
Find the Right Page
| If you want to | Read |
|---|---|
| Check the .NET, .NET Framework, Windows and Visual Studio versions | System Requirements |
| Choose between x86, x64 and AnyCPU builds | 32-bit and 64-bit Applications |
| Download and run the setup, or install a service pack | Installing the Product |
| See what the NuGet package contains | Package Overview |
| Add the offline source or the private feed to a project or a build server | Configuring Package Sources |
| Install or update the package | Installing and Updating Packages |
| Find the toolbox tab and connect the bars and ribbon tabs | Visual Studio Toolbox and XAML Designer |
| Map the controls in XAML and find the assembly of a class | Assemblies and XAML Namespaces |
| Learn how your license reaches the project | Development Licenses |
| Use the editor in a user control library | Application Licensing |
| Build on a build server or in a pipeline | Build Servers |
| Move a project from an earlier version or from the .NET Framework | Upgrade Guide |
After Installation
- Getting Started: tutorials that build your first WPF editor window.
- Deployment Guide: the files your application ships and how to publish it.
- Installation and Package Restore: what to check when the setup or a package restore fails.