diff --git a/_contentTemplates/common/general-info.md b/_contentTemplates/common/general-info.md index 8e7bdb273c..4d7fd98234 100644 --- a/_contentTemplates/common/general-info.md +++ b/_contentTemplates/common/general-info.md @@ -13,7 +13,7 @@ the `Format` is culture-specific and the same format may produce different resul #cdn You can reference the built-in Telerik assets from a cloud CDN instead of a local resource on your server. ->caption Reference the Telerik assets from the cloud in a `WebAssembly` app +>caption Reference the Telerik assets from the cloud CDN ````CSHTML @@ -22,14 +22,14 @@ You can reference the built-in Telerik assets from a cloud CDN instead of a loca . . . - + - + . . . @@ -37,37 +37,11 @@ You can reference the built-in Telerik assets from a cloud CDN instead of a loca ```` ->caption Reference the Telerik assets from the cloud in a `Server-side` app -````CSHTML - - - - . . . - - - - - - - - - - . . . - - -```` - ->important Make sure that the version in the JS file URL matches the version of the Telerik UI for Blazor package. - ->note You may want to monitor the [release notes](https://www.telerik.com/support/whats-new/blazor-ui/release-history) to see when a release uses newer Themes. This will let you point the CDN to a particular version of the themes that is tested and supported with this release, instead of `@latest`. If you don't upgrade for longer periods of time, cumulative changes in the themes may cause the `@latest` to have issues with old rendering from old versions. You can also find the Themes releases and their dates in the [Themes Repo Releases section](https://github.com/telerik/kendo-themes/releases) to match them against the Telerik UI for Blazor releases. +>important Make sure that the version in the URLs matches the version of the Telerik UI for Blazor package. >tip If you decide to use a CDN over static assets, you may want to implement a [fallback]({%slug common-kb-cdn-fallback%}) in case it is unavailable to your users. ->note We are considering a better CDN option for the themes. Until then, you can use the unpkg workaround above, or local dependency management as described below. #end diff --git a/knowledge-base/cdn-fallback.md b/knowledge-base/cdn-fallback.md index d110a81f24..2ef1276da2 100644 --- a/knowledge-base/cdn-fallback.md +++ b/knowledge-base/cdn-fallback.md @@ -34,7 +34,7 @@ This article contains three examples: The Telerik themes provide a test class you can easily test against to determine if they are loaded. To implement a fallback, test an element for this class (`k-theme-test-class`) and see if its `opacity` is `0`. If not, then the Telerik Theme isn't loaded, so you must add a `` element pointing to a local asset that can be downloaded instead. This approach can work in a server-side app as well, and can also be combined with a script fallback logic below. ````CSHTML - + + @@ -84,7 +84,7 @@ var themeChanger = { async Task ChangeTheme() { // use the new URL you will use - it can be relative and/or point to a custom theme - string newThemeUrl = "https://unpkg.com/@progress/kendo-theme-material@latest/dist/all.css"; + string newThemeUrl = "https://blazor.cdn.telerik.com/blazor/{{site.uiForBlazorLatestVersion}}/kendo-theme-material/all.css"; // call the JS interop that will switch out the element await JsInterop.InvokeVoidAsync("themeChanger.changeCss", new[] { newThemeUrl }); } diff --git a/troubleshooting/csp.md b/troubleshooting/csp.md index d188d54863..221143ec2b 100644 --- a/troubleshooting/csp.md +++ b/troubleshooting/csp.md @@ -26,8 +26,8 @@ These limitations can adversely affect the Telerik UI for Blazor components, bec ````HTML ```` diff --git a/upgrade/overview.md b/upgrade/overview.md index 1aa390d7a8..ceef8a0411 100644 --- a/upgrade/overview.md +++ b/upgrade/overview.md @@ -37,17 +37,21 @@ To upgrade the Telerik UI for Blazor components used in your project, perform th 1. Update the version of the `Telerik.UI.for.Blazor` package your project references. If you are using a trial version, the package name is `Telerik.UI.for.Blazor.Trial`. -1. 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 `{{site.uiForBlazorLatestVersion}}` version, the CDN link must be: +1. If you are using our CDN, update the version in the URLs. It must match the version of the package itself. For example, if you are upgrading to the `{{site.uiForBlazorLatestVersion}}` version, the CDN links must look like: **HTML** - + - Generally, the URL has the following format: + + + Generally, the URLs have the following format: **HTML** - + + + ## Upgrade from Trial to Commercial @@ -57,6 +61,8 @@ If you have just purchased a license and you need to migrate from the trial pack 1. Replace the reference to the `Telerik.UI.for.Blazor.Trial` package in your project with a reference to the `Telerik.UI.for.Blazor` package. + * If you are referencing other Telerik trial packages that you now have a license for, remove the `.Trial` from their names too. + 1. If you are using static assets for our JS Interop file and/or Theme, update their path to match the package name (remove the `.Trial` part): **HTML**