License Configuration
With TX Text Control .NET for WPF, there is no license server to set up and no activation dialog to click through. A license is assigned to each developer in the Text Control account, it arrives in the project with the NuGet package or through licenses.licx, and the build compiles it into your application. Follow that path below, from the developer's machine to a user control library and a build server.
How Licensing Works
- A serial number per developer. The account owner assigns it in Manage Products. See Development Licenses.
- The license is compiled in. .NET 8 or higher projects embed txtextcontrol.wpf.license from the package
TXTextControl.TextControl.WPF.SDK. .NET Framework projects compile the entries of licenses.licx with the license compiler. - Users need nothing. The application carries its license and is distributed royalty-free. If the
TextControlorServerTextControlruns in a library,EntryAssemblynames 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 an internal feed. See Build Servers.
The licensing model and the terms behind these rules are explained in Licensing Overview.
Find the Right Page
| If you want to | Read |
|---|---|
| Assign a serial number, or understand txtextcontrol.wpf.license and licenses.licx | Development Licenses |
Put the editor into a user control library or ServerTextControl into a class library, or check what must not ship | Application Licensing |
| Compile on a build server or in a CI/CD pipeline | Build Servers |
| Fix "The following control could not be licensed" | Licensing in Troubleshooting |
Where to Start
Start with Development Licenses. It explains the two ways a license reaches a project, which the other two pages build on.
Pages in This Section
- Development Licenses: serial number assignment, the license file of the package, licenses.licx and the trial version.
- Application Licensing:
EntryAssemblyfor user controls and class libraries, editions at run time, and what stays out of your installer. - Build Servers: the license rules for build servers, the private feed in a pipeline and Azure Artifacts.