# Build Servers

> Build servers and CI/CD pipelines need no extra TX Spell .NET license: restore TXTextControl.TXSpell.WPF.SDK from the private NuGet feed or your own feed.

- **Product:** TX Spell .NET for WPF
- **Section:** Documentation
- **Kind:** Topic
- **Path:** TX Spell .NET for WPF > Installation Guide > License Configuration > Build Servers
- **549 words**
- **Web URL:** https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/licensing/build-servers/
- **LLMs URL:** https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/licensing/build-servers/llms.txt
- **LLMs-Full URL:** https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/licensing/build-servers/llms-full.txt

---

A build server compiles your application with TX Spell .NET for WPF without anyone developing on it. It needs no developer license of its own, and it gets the license the same way as every build does: from the NuGet package it restores. What it needs is access to the packages, which are not on nuget.org.

### Do Build Servers Need a License?

No separate developer license is needed for a build server or a CI/CD system that compiles, tests or packages your application, as long as:

- every developer who works with code that uses TX Spell .NET has a developer license, and
- the build environment is not used for interactive development.

You may use the official NuGet packages of TX Spell .NET in your development, build, deployment and CI/CD processes.

### How a Build Gets the License

In a project for .NET 8 or higher, the license file is part of the NuGet package and is embedded when the project is built. A build server that restores the package therefore builds licensed applications, with no license step of its own. It needs one of these package sources:

| Source | How the build server reaches it |
|---|---|
| Text Control Private NuGet Feed | With the email address of a licensed developer and an API token, stored as secrets of the pipeline |
| Your own feed | A repository in your organization, such as Azure Artifacts, into which you push the packages from the offline folder of a development machine |

The private feed serves `TXTextControl.TXSpell.WPF.SDK` to licensees of TX Spell .NET for WPF, and it was updated with the packages of Service Pack 1. Access to it is provided during an active subscription; packages you obtained during the subscription may be kept and used, also in an internal repository. [Configuring Package Sources](https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/nuget/sources/llms-full.txt) shows the *nuget.config* for both sources.

### Rules for Your Own Feed

An internal package repository or mirror is allowed if it serves only your licensed developers and your automated build systems. Don't publish the packages, or a mirror of them, to anyone outside, and keep the *nuget.config* with credentials out of source control.

### Target Runtime

WPF applications build on Windows agents. When the application uses TX Text Control as well, publish it with a target runtime such as `win-x64`; TX Spell .NET alone needs none. [Windows Versions](https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/requirements/windows/#publishing-with-and-without-tx-text-control) explains the difference.

### Related Pages

- [Configuring Package Sources](https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/nuget/sources/llms-full.txt): the private feed and your own feed.
- [Development Licenses](https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/licensing/development/llms-full.txt): the license file of the package.
- [Installation and Package Restore](https://docs.textcontrol.com/tx-spell-dotnet-wpf/troubleshooting/installation/llms-full.txt): when a package isn't found.

---

## Nearby

- **Previous:** [Application Licensing](https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/licensing/application/llms-full.txt)
- **Next:** [Upgrade Guide](https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/upgrading/llms-full.txt)