Content deleted Content added
New ASP.NET Core 5, not to be confused with older (subject title I see here): "ASP.NET 5 is dead - Introducing ASP.NET Core 1.0 and .NET Core 1.0". Note, .NET Core itself has been renamed to just .NET, and for Blazor dropping some support for older web browsers (those still fully supported if Blazor not used?). New version is up to 36% faster, or even 44.6% (both througput ratios), while the latter has 66.7% latency reduction (do those numbers match?). Some stuff needs to be filled in. |
refspam |
||
Line 38:
The framework is a complete rewrite that unites the previously separate [[ASP.NET MVC]] and [[ASP.NET Web API]] into a single [[programming model]].
Despite being a new framework, built on a new web stack, it does have a high degree of concept compatibility with ASP.NET. ASP.NET Core applications supports side by side versioning in which different applications, running on the same machine, can target different versions of ASP.NET Core. This is not possible with previous versions of ASP.NET.
[[Blazor]] is a recent (optional) component to support [[WebAssembly]] and since version 5.0 it's dropping support for some old web browsers. While current [[Microsoft Edge]] works, the [[legacy system|legacy version]] of it, i.e. "[[Microsoft Edge|Microsoft Edge Legacy]]" and [[Internet Explorer 11]] are dropped when you use Blazor.<ref>{{Cite web|title=[Discussion] Updated Blazor browser support for .NET 5 · Issue #26475 · dotnet/aspnetcore|url=https://github.com/dotnet/aspnetcore/issues/26475|access-date=2020-11-11|website=GitHub|language=en}}</ref>
| |||