You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _contentTemplates/common/get-started.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@
29
29
30
30
#after-you-run-vanilla
31
31
32
-
>tip Make sure that you have {{site.supportedFrameworkVersion}} and [Visual Studio 2019 Preview](https://visualstudio.microsoft.com/vs/preview/) installed.
32
+
>tip Make sure that you have [{{site.supportedFrameworkVersion}}](https://dotnet.microsoft.com/download/dotnet-core/3.1) and [Visual Studio 2019](https://visualstudio.microsoft.com/vs/) installed.
33
33
>
34
34
> The latest version of Telerik UI for Blazor is `{{site.uiForBlazorLatestVersion}}` and it supports `{{site.supportedFrameworkVersion}}`.
Copy file name to clipboardExpand all lines: getting-started/client-blazor.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,11 @@ This article explains how to get the Telerik UI for Blazor components in your **
18
18
*[Add to an Existing Project](#add-to-existing-project)
19
19
1.[Add a Telerik Component to a View](#add-a-telerik-component-to-a-view)
20
20
21
-
>note You can follow the progress of a WASM flavor supported officially by Microsoft in the following links: [Milestone](https://github.com/aspnet/AspNetCore/milestone/58) and [Project](https://github.com/orgs/aspnet/projects/32). You can still work on client-side Blazor apps in the meantime, but there may be changes in the framework.
21
+
22
+
>caution The latest version of Telerik UI for Blazor is `{{site.uiForBlazorLatestVersion}}` and it supports `WASM .NET Core 3.1 Preview 3` and not the latest `WASM .NET Core 3.1 Preview 4` because of severe issues in the Linker. You can read more about this in the [Framework Versions Support]({%slug framework-versions-support%}) article.
23
+
>
24
+
>To run a WASM project with the Telerik components, keep the WASM NuGet package references pointing to the `3.1.0-preview3.19555.2` version.
Copy file name to clipboardExpand all lines: upgrade/framework-versions.md
+20-2Lines changed: 20 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,17 +12,35 @@ position: 5
12
12
13
13
This article lists the .NET Core versions supported by the UI for Blazor suite, and which versions of the Telerik UI for Blazor work under which framework versions.
14
14
15
-
>note We currently support only the latest available version of UI for Blazor (**{{site.uiForBlazorLatestVersion}}**) and the .NET Core 3 SDK (**{{site.supportedFrameworkVersion}}**) on the [Server-side](https://docs.telerik.com/blazor-ui/getting-started/server-blazor) flavor. On the [WebAssembly](https://docs.telerik.com/blazor-ui/getting-started/client-blazor) flavor, `.NET Core 3.1 preview 3` is supported, because in the `.NET Core 3.1 preview 4 of WASM`, the linker breaks extension methods that our components require.
15
+
Telerik supports only the latest available version of UI for Blazor (**{{site.uiForBlazorLatestVersion}}**).
16
+
17
+
## Serve-side Blazor
18
+
19
+
>caption Telerik UI for Blazor versions per framework version for the server-side flavor
The client-side (WASM) flavor of Blazor is not part of the .NET Core 3.1 framework. It is not supported by Microsoft yet and it ships as preview NuGet packages that you reference in your projects. While the release dates and numbers of the WASM flavor often match with the .NET Core versions and releases, they are separate products at the moment.
33
+
34
+
>caption Telerik UI for Blazor versions per WASM Preview version
35
+
36
+
| WASM Preview version | Telerik UI for Blazor version |
| .NET Core 3.1 preview 4 (release date matches .NET Core 3.1 GA) | N/A - there are major issues in the Linker that prevent our code from working in this version. |
0 commit comments