Telerik UI for ASP.NET MVC Licensing
Progress® Telerik UI for ASP.NET MVC is available under a developer (commercial) or a trial license.
Regardless of the license version you hold, to use Telerik UI for ASP.NET MVC, you have to agree to the End User License Agreement.
You can find the license agreement in your Telerik controls installation folder under \license-agreements\EULA.rtf. For example, the default location for the Q4 2024 release is C:\Program Files (x86)\Progress\Telerik UI for ASP.NET MVC 2024 Q4\license-agreements\EULA.rtf.
Bill of Materials and Third-Party Software Licensing
You can find a Bill of Materials (BOM) and a list of the third-party software, including open-source software, in the \LicenseAgreements\ThirdParty\NOTICE.txt location in your Telerik controls installation folder. For example, the default location for the Q4 2024 release is C:\Program Files (x86)\Progress\Telerik UI for ASP.NET MVC 2024 Q4\license-agreements\third-party\NOTICE.txt. For versions prior to R2 2018 SP1, the file is called licenses.txt.
Current Licensing Mechanism
Starting with the 2025 Q1 release, Telerik UI for ASP.NET MVC requires activation through a license key (trial or commercial). To download your personal activation key and activate the Telerik UI for ASP.NET MVC components, follow License Key Installation steps.
An invalid license results in errors and warnings during build and run-time indicators such as watermarks and banners.
License.licx in Old Product Versions
As of the Q1 2015 release, Telerik® UI for ASP.NET MVC uses the standard .NET licensing mechanism—if you use Telerik® UI for ASP.NET MVC items in design-time, Visual Studio adds a license.licx file to the solution. This file is used only in design-mode and is not needed for deployment explicitly. The .NET framework (lc.exe) will embed it in the assembly when your application is built for deployment.
The license.licx license file is maintained by Visual Studio and contains information about all licensed components in the application, including non-Telerik products. Having this license file is not expected to bring any performance or compilation issues and you can ignore it.
If your project build fails with errors which point to the license file, you can delete it and rebuild. Alternatively, you can clear its contents and mark it as Read Only.
If you are working under source control, once the file is created, it will be detected as a change by your source control system. Telerik suggests that you check in this file initially. When the file is checked out again during your work, it is up to you to decide whether to check it in, or discard the changes.