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: upgrade/framework-versions.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,13 +57,13 @@ While the release dates and numbers of the WASM flavor often match with the .NET
57
57
58
58
## .NET 5
59
59
60
-
The future of .NET Core will eventually be through .NET 5. Its [first preview](https://devblogs.microsoft.com/dotnet/announcing-net-5-0-preview-1/) is already available.
60
+
The future of .NET Core will eventually be through .NET 5. Its [third preview](https://devblogs.microsoft.com/aspnet/asp-net-core-updates-in-net-5-preview-3/) is already available.
61
61
62
-
The Telerik UI for Blazor suite is committed to the WASM flavor of Blazor and we need to make sure we are compatible with its own previews (at the moment - .NET Core 3.2.0-preview3.20168.3) and subsequently - its official version.
62
+
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 previews (at the moment - .NET Core 3.2.0-preview5.20216.8) and subsequently - its official version.
63
63
64
-
Thus, we cannot guarantee compatibility with the .NET 5 previews.
64
+
We cannot guarantee compatibility with the .NET 5 previews.
65
65
66
-
The situation may be revised after the client-side (WASM) implementation of Blazor becomes official.
66
+
The situation may be revised after the client-side (WebAssembly) implementation of Blazor becomes official.
0 commit comments