Skip to content

Commit 8dae9d2

Browse files
docs(common): .net 5 support
1 parent c33a90d commit 8dae9d2

File tree

3 files changed

+21
-17
lines changed

3 files changed

+21
-17
lines changed

_config.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -432,8 +432,8 @@ intro_columns:
432432
baseurl: /blazor-ui
433433

434434
## Latest UI for Blazor version. Used in some articles
435-
uiForBlazorLatestVersion: "2.18.0"
436-
supportedFrameworkVersion: ".NET Core 3.1.9"
435+
uiForBlazorLatestVersion: "2.19.0"
436+
supportedFrameworkVersion: ".NET Core 3.1.9 and .NET 5"
437437

438438
## The Kendo UI version used
439439
cdnVersion: "2019.1.115"

_contentTemplates/common/get-started.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
## Step 1 - Set Up a Blazor Project
33

44

5-
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.
5+
Make sure that you have [.NET Core 3.1.x](https://dotnet.microsoft.com/download/dotnet-core/3.1) or [.NET 5](https://dotnet.microsoft.com/download/dotnet/5.0), and [Visual Studio 2019](https://visualstudio.microsoft.com/vs/) installed.
66

77
The latest version of Telerik UI for Blazor is `{{site.uiForBlazorLatestVersion}}` and it supports `{{site.supportedFrameworkVersion}}`.
88

upgrade/framework-versions.md

Lines changed: 18 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,24 @@ This article lists the .NET Core versions supported by the UI for Blazor suite,
1414

1515
>note Telerik supports only the latest available version of UI for Blazor (**{{site.uiForBlazorLatestVersion}}**).
1616
17-
Telerik UI for Blazor targets `netstandard2.1` in order to be compatible with the WASM flavor. Thus, apps/libraries that reference our package must target `netstandard2.1` or `netcoreapp3.1`. These are the standard target frameworks for, respectively, WASM and Server Blazor projects, but Razor class libraries target `netstandard2.0` by default so you would need to update it.
17+
Telerik UI for Blazor targets `netstandard2.1`. Thus, apps/libraries that reference our package must target `netstandard2.1`, `netcoreapp3.1` or `net5.0`. Razor Class Libraries may target `netstandard2.0` by default so you would need to update that.
1818

19-
## Serve-side Blazor
19+
20+
21+
## .NET 5
22+
23+
Telerik UI for Blazor supports .NET 5 since its `2.19.0` release.
24+
25+
| .NET 5 | Telerik UI for Blazor version |
26+
|------------|--------------------------------------------------------|
27+
| .NET 5 RTM | {{site.uiForBlazorLatestVersion}} |
28+
29+
30+
31+
32+
## .NET Core 3.1
33+
34+
### Serve-side Blazor
2035

2136
>caption Telerik UI for Blazor versions per framework version for the server-side flavor
2237
@@ -30,7 +45,7 @@ Telerik UI for Blazor targets `netstandard2.1` in order to be compatible with th
3045
| .NET Core 3.0 RTM | 2.1.0, 2.1.1 |
3146

3247

33-
## Client-side Blazor
48+
### Client-side Blazor
3449

3550
The client-side (WebAssembly) flavor of Blazor is a set of separate NuGet packages whose version may not match the .NET Core version they run on.
3651

@@ -58,17 +73,6 @@ The client-side (WebAssembly) flavor of Blazor is a set of separate NuGet packag
5873

5974

6075

61-
## .NET 5
62-
63-
The future of .NET Core will eventually be through .NET 5. Its [Second Release Candidate](https://devblogs.microsoft.com/aspnet/asp-net-core-updates-in-net-5-release-candidate-2/) is already available.
64-
65-
The Telerik UI for Blazor suite is committed to the WebAssembly flavor of Blazor and we need to make sure we are compatible with its own main line of releases (at the moment - .NET Core 3.2.1).
66-
67-
We cannot guarantee compatibility with the .NET 5 previews.
68-
69-
The situation may be revised at a later time.
70-
71-
7276
## See Also
7377

7478
* [Old Versions Support Policy]({%slug old_versions_support_policy%})

0 commit comments

Comments
 (0)