This article explains how to upgrade to a new version of Telerik UI for Blazor.
To upgrade the Telerik components, you need to update their NuGet package reference, and, if you use them, the CDN links.
The latest available version of UI for Blazor is 2.18.0.
Before starting an upgrade of your project, you may find it useful to review the following information:
- Framework Versions Support - this will let you see what version of the .NET framework you need and which UI for Blazor versions work on it.
- UI for Blazor Release History — reviewing the release notes for all releases you go through will let you see what has changed, what fixes, features and components have been implemented so you are better prepared to meet your project's challenges.
- Whether you are affected by a breaking change. The List of Telerik UI for Blazor Versions with Breaking Changes article shows which releases of our component suite have breaking changes. Review the information for the releases you go through so you can evaluate whether you will be affected by anything.
In this article:
To upgrade the Telerik UI for Blazor components used in your project, perform the following steps:
Update the version of the
Telerik.UI.for.Blazorpackage your project references. If you are using a trial version, the package name is
If you are using our CDN for the JS Interop file, update the version in its URL. It must match the version of the package itself. For example, if you are upgrading to the
2.18.0version, the CDN link must be:
<script src="https://kendo.cdn.telerik.com/blazor/2.18.0/telerik-blazor.min.js" defer></script>
Generally, the URL has the following format:
<script src="https://kendo.cdn.telerik.com/blazor/<VERSION NUMBER>/telerik-blazor.min.js" defer></script>
If you have just purchased a license and you need to migrate from the trial package to the licensed version, perform the following steps:
Replace the reference to the
Telerik.UI.for.Blazor.Trialpackage in your project with a reference to the
If you are using static assets for our JS Interop file and/or Theme, update their path to match the package name (remove the
<!-- FROM <script src="_content/Telerik.UI.for.Blazor.Trial/js/telerik-blazor.js" defer></script> TO --> <script src="_content/Telerik.UI.for.Blazor/js/telerik-blazor.js" defer></script> <!-- FROM <link rel="stylesheet" href="_content/Telerik.UI.for.Blazor.Trial/css/kendo-theme-default/all.css" /> TO --> <link rel="stylesheet" href="_content/Telerik.UI.for.Blazor/css/kendo-theme-default/all.css" />
The Trial version of our assembly has the
Telerik.Blazor Trial version Title. You can see it by Right clicking the assembly > Properties > File Description. You can find the assembly by extracting the
.nupgk file like a
.zip archive, or in the publish location.
If you have a license, but you still see the trial message, especially after publishing an app to a staging or live server, the
Telerik.Blazor.dll assembly that the build used is still the trial one.
Thank you for using the Trial Version of Telerik UI for Blazor to build more powerful applications faster. Purchase the Commercial Version now to get access to all product updates and the Telerik expert support.
The most common reason for the problem is that the framework decides to incorrectly copy a trial version of our assembly into the
dist folder of the app, even though it puts the correct licensed version at the root of the publish folder. This seems like a problem in the build process of the framework, and hopefully it will get fixed in future versions.
To fix this in the meantime, try the following process (you can try a new test build after each step where you make a change):
Ensure that the licensed package is referenced in the project (
Telerik.UI.for.Blazor.Trial). Make sure this is also the case on the build machine. Sometimes a failed build or locked files may prevent a file from being updated and so the build machine may be using a trial reference.
Uninstall any Trial installations from the build machine, dev PC and live server.
If you have created local NuGet feeds, ensure they do not contain Trial versions of our packages.
Clean the NuGet packages on the build machine, dev PC and live server.
Clean the projects.
objfolders where packages and assemblies may be cached.