TX Text Control .NET for Windows Forms

License Configuration

Topic

Your license of TX Text Control .NET for Windows Forms is not activated online or managed in files by hand: it travels with your projects and is compiled into the applications you build. Where it comes from and where it ends up differs between a developer's project, a class library and a build server, and each of the three cases is described on a page of its own.

How Licensing Works

  • Each developer has a license assigned in the Text Control account. See Development Licenses.
  • The license is compiled into your application. In .NET projects, the NuGet package brings the license file txtextcontrol.winforms.license. In .NET Framework projects, the license compiler builds the license from licenses.licx.
  • Your users need nothing. Applications are distributed royalty-free, and they carry their license. When TX Text Control is used in a class library, EntryAssembly names the assembly that holds the license. See Application Licensing.
  • Build servers need no license of their own. They restore the licensed package from the private feed or your own feed. See Build Servers.

Licensing Overview explains the licensing model and the license agreement behind these rules.

Find the Right Page

If you want toRead
Assign a license to a developer, or understand the license file and licenses.licxDevelopment Licenses
Use TX Text Control in a class library, a user control or a unit test, or check what must not shipApplication Licensing
Build on a build server or in a CI/CD pipelineBuild Servers

Where to Start

Read Development Licenses first: it explains the two ways a license reaches a project, which the other pages build on. If a license is not found, see Licensing in Troubleshooting.