# Text Control Private NuGet Feed > Install licensed TX Text Control packages from the private NuGet feed: feed URL, email and API token authentication, license injection and a first package. - **Product:** TX Text Control .NET Server - **Section:** Documentation - **Kind:** Topic - **Path:** TX Text Control .NET Server > Installation Guide > NuGet Packages > Text Control Private NuGet Feed - **1154 words** - **Web URL:** https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/private-feed/ - **LLMs URL:** https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/private-feed/llms.txt - **LLMs-Full URL:** https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/private-feed/llms-full.txt --- The Text Control Private NuGet Feed delivers the licensed TX Text Control packages to your projects. Installing a licensed package works like installing any other NuGet package: you add the feed to NuGet with a `nuget.config` file, install the package and build. The following pages help licensed developers who set up Visual Studio, the .NET CLI or a build pipeline, and account holders who give their developers access. Your license comes with the engine packages of the feed, `TXTextControl.TextControl.Core.SDK` and `TXTextControl.TextControl.ASP.SDK`, which every project references. There are no activation dialogs, no license files to manage and no additional configuration steps, and the same feed works in Visual Studio, on the command line and on build servers. ### How the Feed Works - **Feed URL and source name.** The feed is available at `https://www.textcontrol.com/nuget/v3/index.json`. In `nuget.config` and in Visual Studio, the package source is named `TextControl`. - **Authentication.** NuGet authenticates with the email address of the assigned developer and an API token. The account holder creates the token in the Text Control account, and the developer receives a personalized `nuget.config` file that contains these credentials. - **All your licenses in one feed.** The email address connects to all serial numbers assigned to it. A developer with a TX Text Control .NET Server license and a TX Text Control .NET for WPF license, for example, sees the packages of both products in the same feed. - **Only licensed packages.** Developers only see the packages and versions they are licensed for. For example, a developer who is licensed for TX Text Control .NET Server and TX Text Control .NET for WPF does not see `TXTextControl.TextControl.WinForms.SDK`. - **License injection.** When NuGet downloads a package, the server injects the license into the package before the download. The package is ready to use as soon as it is installed. ### Who Can Use the Feed The feed is available for all customers with active licenses. To use it: - A serial number must be assigned to your email address. The account holder assigns serial numbers in **Manage Products** in the Text Control account. If you are a developer without an assigned serial number, ask your account holder. - TX Text Control is licensed per developer, also when a build server restores the packages. See [Development Licenses](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/licensing/development/#per-developer-licensing). For questions about licenses and subscriptions, contact the [Text Control sales team](https://www.textcontrol.com/contact/). To evaluate the product without a license, install the trial version, which provides the packages in the local [Text Control Offline Packages](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/offline-packages/llms-full.txt) source. ### Packages on the Feed The feed contains the engine packages `TXTextControl.TextControl.Core.SDK` and `TXTextControl.TextControl.ASP.SDK`, the Document Editor backend `TXTextControl.Web.DocumentEditor.Backend` and the web packages `TXTextControl.Web`, `TXTextControl.Web.DocumentViewer` and `TXTextControl.Web.DocumentViewer.Classic`, together with the packages of the Windows Forms and WPF products for developers licensed for them. [Package Overview](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/packages/#packages-at-a-glance) describes each package and explains which packages your project needs. ### Get Started in Three Steps 1. **Get your `nuget.config` file.** When the account holder assigns a serial number to you, an API token is created and you receive an email with a download link for your personalized `nuget.config`. Copy the file to your project. See [Creating an API Token](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/private-feed/api-token/llms-full.txt) and [nuget.config](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/private-feed/nuget-config/llms-full.txt). 2. **Install a package.** Run `dotnet add package` with the package name, or select the **TextControl** package source in the Visual Studio NuGet Package Manager: ```bash dotnet add package TXTextControl.TextControl.Core.SDK ``` 3. **Build and run your application.** NuGet retrieves the package from the feed with the credentials in `nuget.config`, and the package already contains your license. ### Choose a Page | If you want to | Read | |---|---| | Create API tokens for your developers, or understand how long a token is valid | [Creating an API Token](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/private-feed/api-token/llms-full.txt) | | Understand the `nuget.config` file, where to put it and how to keep it out of source control | [nuget.config](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/private-feed/nuget-config/llms-full.txt) | | Install packages in Visual Studio 2022 or 2026 | [Visual Studio](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/private-feed/visual-studio/llms-full.txt) | | Search and install packages from the command line | [.NET CLI](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/private-feed/dotnet-cli/llms-full.txt) | | Restore packages in GitHub Actions, GitLab, Azure DevOps, Jenkins, Bitbucket, TeamCity or Docker | [CI/CD Authentication](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/private-feed/ci-cd/llms-full.txt) | | Solve authentication problems | [NuGet Authentication](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/nuget-authentication/llms-full.txt) | The announcement [Text Control Private NuGet Feed](https://www.textcontrol.com/blog/2026/02/09/text-control-private-nuget-feed/) on the Text Control blog introduces the feed. --- ## In This Section - [Creating an API Token](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/private-feed/api-token/llms-full.txt): Create API tokens for the private NuGet feed by assigning a serial number in Manage Products or manually, and manage their validity of 365 or up to 730 days. - [CI/CD Authentication](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/private-feed/ci-cd/llms-full.txt): Restore packages from the Text Control Private NuGet Feed with secrets in GitHub Actions, GitLab, Azure DevOps, Jenkins, Bitbucket, TeamCity and Docker. - [.NET CLI](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/private-feed/dotnet-cli/llms-full.txt): Run dotnet package search, dotnet add package and dotnet restore against the private NuGet feed on Windows and Linux, in VS Code or on a build server. - [nuget.config](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/private-feed/nuget-config/llms-full.txt): Configure nuget.config for the private NuGet feed: packageSources, packageSourceCredentials, where NuGet finds the file, and keeping the API token out of Git. - [Visual Studio](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/private-feed/visual-studio/llms-full.txt): Install TX Text Control packages from the TextControl source in the NuGet Package Manager of Visual Studio 2022 or 2026, and fix a source that doesn't show up. --- ## Nearby - **Previous:** [Package Overview](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/packages/llms-full.txt) - **Next:** [Creating an API Token](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/nuget/private-feed/api-token/llms-full.txt)