The Licensing process of our ComponentOne controls is fairly simple. For most licensing scenarios, all you need to do is activate your serial key. With an activated license you can build and distribute any number of .NET applications using ComponentOne controls. For more information, see Activating a Serial Key.
License activation for a standard developer key is limited to 3 different machines, and up-to 9 reactivations per day (a reactivation is the process of deactivating and reactivating again). Your 3 activations may include a separate build machine, but if you are using a dynamic build agent in which the machine is reset constantly, you may consider purchasing a special pipeline license. For more information, see Pipeline Licensing.
The application licensing is handled automatically by Visual Studio which obtains version and licensing information from the component when it is added to a form at design-time from the toolbox or at build-time from the NuGet package build script. When queried by Visual Studio, the component looks for licensing information stored in the system and generates a run-time license and version information, which Visual Studio saves in one of the following two files added to the project:
An embedded resource file which contains the actual run-time license (*.exe.licenses, *.dll.licenses, or *.gclicx)
A licenses.licx file that contains the licensed component strong name and version information (.NET Framework only)
If you are using a ComponentOne version newer than 2020 v2 (x.x.20202.x) released in July 2020, then the runtime license will be named .gclicx. The gclicx file will either be added to the project solution as an embedded resource, or it may only appear in the build output. In either case, this file must be distributed with the application. For more information, see Licensing Applications.
The runtime license file (.gclicx) will only work for the application in which its built. The calling application name is embedded within the file and must always match. If you are building a user control for a different named application, you may need a plugin license. For more information, see License User Controls.
