# Public NuGet Packages > Install TX Text Control packages from nuget.org: the Blazor DocumentEditor and DocumentViewer components, Markdown.Core, PDF.Validation and ParallelMailMerge. - **Product:** TX Text Control .NET Server - **Section:** Documentation - **Kind:** Topic - **Path:** TX Text Control .NET Server > Installation Guide > NuGet Packages > Public NuGet Packages - **1879 words** - **Web URL:** https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/public-packages/ - **LLMs URL:** https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/public-packages/llms.txt - **LLMs-Full URL:** https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/public-packages/llms-full.txt --- Some TX Text Control packages are published on nuget.org, the public NuGet gallery, under the profile [txtextcontrol](https://www.nuget.org/profiles/txtextcontrol). The ones that belong to TX Text Control .NET Server are described below, with what they need and how they work together with the licensed packages from the Text Control Private NuGet Feed. ### Packages on nuget.org | Package | Purpose | |---|---| | `TXTextControl.Web.Blazor.DocumentEditor` | Document Editor component for Blazor Web Apps | | `TXTextControl.Web.Blazor.DocumentViewer` | Document Viewer component for Blazor Web Apps | | `TXTextControl.Markdown.Core` | Load and save Markdown with TX Text Control | | `TXTextControl.PDF.Validation` | Validate PDF/UA documents | | `TXTextControl.DocumentServer.ParallelMailMerge` | Run `MailMerge` operations in isolated worker processes | | `TXTextControl.Web` | Document Editor for ASP.NET Core, also on the private feed | | `TXTextControl.Web.DocumentViewer` | Document Viewer (Core engine), also on the private feed | | `TXTextControl.Web.DocumentViewer.Classic` | Document Viewer (Classic engine), also on the private feed | [Package Versioning](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/versioning/#current-versions) lists the current version of each package. `TXTextControl.Web.Collaboration`, a package for real-time collaboration in the Document Editor, is available as a preview. Six prerelease packages add language model features to applications built with TX Text Control .NET Server: `TXTextControl.AI`, `TXTextControl.AI.AspNetCore`, `TXTextControl.AI.Knowledge`, `TXTextControl.AI.LlamaServer`, `TXTextControl.AI.Mcp` and `TXTextControl.AI.McpServer`, all at version 0.1.0-beta.3. Install them with prerelease versions included, and see [Text Control AI](https://docs.textcontrol.com/tx-text-control-dotnet-server/ai/text-control-ai/llms-full.txt) for what each one does. The `txtextcontrol` profile also contains packages of other Text Control products, such as DS Server. They are not part of TX Text Control .NET Server. Most of these packages need the engine package `TXTextControl.TextControl.Core.SDK`, which you install from the [Text Control Private NuGet Feed](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/private-feed/llms-full.txt), or from the [Text Control Offline Packages](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/offline-packages/llms-full.txt) source when you evaluate the trial version. ### Blazor Components #### TXTextControl.Web.Blazor.DocumentEditor - **Purpose:** the files needed to develop a .NET 8.0 or higher Blazor Web App with TX Text Control 34.0 and the Document Editor. The package provides the `DocumentEditor` Razor component, which uses the interactive server render mode. - **NuGet dependencies:** `TXTextControl.Web` 34.4.0 and `Microsoft.AspNetCore.Components.Web` 8.0.11. - **Also install:** `TXTextControl.Web`, `TXTextControl.TextControl.Core.SDK` and `TXTextControl.Web.DocumentEditor.Backend` from the private feed. The Blazor application hosts the Document Editor backend with the `DocumentEditorWorkerManager` hosted service and the WebSocket middleware. - **Tutorial:** [Blazor](https://docs.textcontrol.com/tx-text-control-dotnet-server/getting-started/document-editor/blazor/llms-full.txt). #### TXTextControl.Web.Blazor.DocumentViewer - **Purpose:** a Blazor component for the Document Viewer. The page that contains the component needs interactive server rendering, for example `@rendermode InteractiveServer`. - **NuGet dependencies:** `Microsoft.AspNetCore.Components.Web` 8.0.11. - **Also install:** a backend service is required. To host it in the Blazor application, install `TXTextControl.Web.DocumentViewer` and `TXTextControl.TextControl.Core.SDK`, add the controllers with `builder.Services.AddControllers()`, and call `app.UseRouting()` and `app.UseTXDocumentViewer()`. To use a backend in another application, set the component's `BasePath` parameter. - **More information:** [Blazor Integration Guide](https://docs.textcontrol.com/tx-text-control-dotnet-server/integration/blazor/llms-full.txt). ### TXTextControl.Markdown.Core - **Purpose:** a .NET 8 library that converts between Markdown and TX Text Control content. It imports and exports complete documents, the current `Selection` and `SubTextPart` content. - **Works with:** `TXTextControl.ServerTextControl` in .NET and ASP.NET Core, and the Windows Forms and WPF `TextControl`. - **Target and dependencies:** `net8.0`, no NuGet dependencies. - **Also install:** a TX Text Control engine package, for example `TXTextControl.TextControl.Core.SDK`. - **Namespace:** `TXTextControl.Markdown`. ```bash dotnet add package TXTextControl.Markdown.Core ``` ### TXTextControl.PDF.Validation - **Purpose:** a .NET library that validates the PDF/UA accessibility characteristics of PDF documents. It returns a structured report with PDF/UA findings, extracted document information and diagnostics for signatures and encryption. - **Requirements:** .NET 10, and read access to the PDF file or the PDF bytes to validate. - **NuGet dependencies:** `System.Security.Cryptography.Pkcs` 9.0.10. - **More information:** [PDF Validation](https://docs.textcontrol.com/tx-text-control-dotnet-server/pdf/validation/llms-full.txt). Add the package reference to your application project: ```xml ``` ### TXTextControl.DocumentServer.ParallelMailMerge - **Purpose:** a `ParallelMailMerge` component that runs TX Text Control `MailMerge` operations in isolated worker processes, so that several independent merge jobs are processed at the same time. - **Target:** `net10.0`. - **NuGet dependencies:** `TXTextControl.TextControl.Core.SDK` 34.0.4 or higher. - **Also install:** `TXTextControl.TextControl.Core.SDK` from the private feed. The consuming application must reference TX Text Control and provide a valid TX Text Control license. ```bash dotnet add package TXTextControl.DocumentServer.ParallelMailMerge dotnet add package TXTextControl.TextControl.Core.SDK ``` The package's README on [nuget.org](https://www.nuget.org/packages/TXTextControl.DocumentServer.ParallelMailMerge/34.0.0) asks you to add the worker handoff `ParallelMailMerge.TryRunWorkerAsync(args)` as the first application code in *Program.cs*. ### TXTextControl.Web.Collaboration (Preview) `TXTextControl.Web.Collaboration` adds server-authoritative real-time collaboration to the ASP.NET Core Document Editor. It is a preview intended for evaluation and early integration feedback. - **Target:** `net10.0`. - **NuGet dependencies:** `TXTextControl.TextControl.Core.SDK` 34.0.4 or higher and `TXTextControl.Web` 34.4.0 or higher. - **Also install:** `TXTextControl.Web.DocumentEditor.Backend`, which the application adds explicitly because it owns the Document Editor backend process. A valid TX Text Control license is required. ### Web Packages on nuget.org and on the Private Feed `TXTextControl.Web`, `TXTextControl.Web.DocumentViewer` and `TXTextControl.Web.DocumentViewer.Classic` are available on nuget.org and on the private feed. Their description on nuget.org says that when the package is installed from nuget.org and not from the local "Text Control Offline Packages" source, the trial version of TX Text Control .NET Server must be installed on the development machine. As a licensed developer, install these packages from the private feed together with the engine package, as the [Getting Started](https://docs.textcontrol.com/tx-text-control-dotnet-server/getting-started/llms-full.txt) tutorials do. ### Install Packages From nuget.org nuget.org needs no credentials. - **Visual Studio:** choose **Manage NuGet Packages...** from the **Project** menu, select **nuget.org** as the **Package source** and install the package. - **.NET CLI:** run `dotnet add package` with the package name in the project folder. If your `nuget.config` contains a `clear` element, it must list nuget.org as a package source, as the structure in [nuget.config](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/private-feed/nuget-config/llms-full.txt) does. Otherwise NuGet cannot find the public packages and their dependencies. ### Next Steps - [Package Overview](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/packages/llms-full.txt) — which packages you need for your scenario. - [Package Versioning](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/versioning/llms-full.txt) — which versions belong together. - [Blazor](https://docs.textcontrol.com/tx-text-control-dotnet-server/getting-started/document-editor/blazor/llms-full.txt) — a Blazor Web App with the Document Editor. --- ## Nearby - **Previous:** [CI/CD Authentication](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/private-feed/ci-cd/llms-full.txt) - **Next:** [Offline Packages](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/offline-packages/llms-full.txt)