NuGet Packages
TX Text Control .NET Server is delivered as NuGet packages. Learn which packages your project needs, where you get them and how their versions work, and how to authenticate against the Text Control Private NuGet Feed in Visual Studio, on the command line and on build servers.
After reading it, you can set up a new project or a build pipeline with the right packages, keep your credentials out of source control, and choose package versions that belong together.
Where the Packages Come From
TX Text Control packages are available from three package sources: the Text Control Private NuGet Feed for customers with active licenses, nuget.org for the Blazor components and the add-on packages, and the local Text Control Offline Packages source that the Windows setup installs. Package Sources describes them, and Packages at a Glance shows which package is available from which source.
A typical application combines packages from the private feed and nuget.org. A Blazor Web App with the Document Editor, for example, installs the engine, the web package and the backend from the private feed and the Blazor component from nuget.org.
Choose a Page
| If you want to | Read |
|---|---|
| Find out which packages your project needs | Package Overview |
| Understand how the private feed works and get access | Text Control Private NuGet Feed |
| Give a developer access to the feed | Creating an API Token |
| Set up the feed in Visual Studio or with the .NET CLI | Visual Studio or .NET CLI |
| Restore packages in a CI/CD pipeline or a Docker build | CI/CD Authentication |
| Use the Blazor, Markdown, PDF validation or parallel mail merge packages | Public NuGet Packages |
| Install packages from the trial setup | Offline Packages |
| Understand version numbers and pin versions | Package Versioning |
Where to Start
If you are new to TX Text Control, read Package Overview first to choose between the Core and the Classic engine and to find the packages for your scenario. Then set up the Text Control Private NuGet Feed and continue with Create Your First Application.
Angular, React and Node.js frontends use npm packages in addition to the NuGet packages. See npm Packages.