Hi,
I recently updated to the 2025 version of telerik. I did it through the nuget option. Followed the steps and added the license file to the roaming directory. So far haven't seen any build errors, no watermarks or popups. I assume everything went smoothly. However, I see a warning, "Telerik and Kendo UI Licensing warning TKL001: No Telerik or Kendo UI product references detected in project." It says that one is to update to 1.4.9. I have 2 sites using this:
- Front site has only aspnet.ajax.net462 installed and the Licensing version has the most latest at 1.4.6. 1.4.9 is not in the drop
- Admin site has aspnet.ajax.net462 installed followed by windows.zip, windows.documents.spreadsheet, windows.documents.spreadsheet.formatprovider.openxml, windows.documents.core, windows.documents.drawingml, windows.documents.spreadsheet, windows.documents.fixed, windows.documents.flow, windows.documents.flow.formatproviders.pdf, and windows.documents.fixed. In this instance I was able to update the licensing version to 1.6.5
In both cases I still see the warning. Is this something I should just ignore?
Even though you have updated the Telerik.Licensing package (1.6.5 in Admin, 1.4.6 in Front), the TKL001 warning still indicates that no Telerik or Kendo UI product references are detected in the project. This can sometimes occur due to project-specific conditions or the environment setup.
To help us investigate further, please add the following line to the .csproj file of the affected projects:
<TelerikLicensingVerbosity>diagnostic</TelerikLicensingVerbosity>
Also, can you confirm which version of Visual Studio you are using? Note that we support Visual Studio 2019 and 2022. If the project is targeting an older .NET version or if it was created in a much older Visual Studio version, it is possible some dependencies required by the licensing task may be missing, leading to this kind of issue.
Looking forward to your response with the log and environment details.
We've reviewed the information and logged a high-priority issue related to the TKL001 warning in Visual Studio 2015. Although VS 2015 is not among the officially supported versions, we understand this use case is important and will investigate the behavior further.
We'll keep you updated on any developments. In the meantime, if the UI controls are functioning properly and no build errors are present, the warning can be considered non-blocking.