Build Servers
A build server compiles your application with TX Spell .NET for Windows Forms 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 restores the package from the Text Control Private NuGet Feed, with the email address of a licensed developer and an API token stored as secrets of the pipeline, or from a feed of your own organization; Configuring Package Sources shows the nuget.config for both.
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
Windows Forms applications build on Windows agents. The target runtime of the publish step is set as for any publish: Publishing .NET Applications describes when it is needed.