This topic applies to licensing .NET Framework 4.5.2+ WinForms, WPF and ASP.NET Web Forms applications for ComponentOne 2020 v2 and newer. For older versions, see Licensing Older .NET Framework Applications. For all options, see Licensing Applications.
Each developer or build machine needs an activated product serial key to build the project and properly license the application. To activate a serial key, see Activating a Serial Key.
Once you activate a serial key, most of the licensing process is handled automatically. Use the information below to better understand how the licensing works to help troubleshoot issues.
ComponentOne .NET Framework controls support the standard licenses.licx file approach supported by the Microsoft .NET LicenseProvider. When you add a .NET Framework control to the Visual Studio designer surface, a design-time licenses.licx file is generated for the project. This file includes version information and must remain updated to reflect the version referenced in the application.
You can create the licenses.licx file manually if controls are added through code or XAML. For detailed steps, see Generate licenses.licx File Manually.
Use the MESCIUS Visual Studio extension to populate or update the licenses.licx file. Select Tools > MESCIUS > Update Projects.
When the application is built on a properly activated machine a unique runtime license file (.gclicx) is generated and embedded with the application. The runtime license file can typically be found in the project folder. This .gclicx file must be distributed with the application as an embedded resource.
You can manually create the run-time license. See Create Runtime License. If working with build agents or user controls, see Additional Licensing Scenarios.
If you continue to see an unlicensed nag screen, see Troubleshooting topics.
