ASP.NET Core is an open-source modular web-application framework. It is a redesign of ASP.NET that unites the previously separate ASP.NET MVC and ASP.NET Web API into a single programming model.[3][4] Despite being a new framework, built on a new web stack, it does have a high degree of concept compatibility with ASP.NET. The ASP.NET Core framework supports side-by-side versioning so that different applications being developed on a single machine can target different versions of ASP.NET Core. This was not possible with previous versions of ASP.NET. ASP.NET Core initially ran on both the Windows-only .NET Framework and the cross-platform .NET. However, support for the .NET Framework was dropped beginning with ASP.Net Core 3.0.[5]

Blazor is a recent (optional) component to support WebAssembly and since version 5.0, it has dropped support for some old web browsers. While current Microsoft Edge works, the legacy version of it, i.e. "Microsoft Edge Legacy" and Internet Explorer 11 was dropped when you use Blazor.[6]

Release history


Originally deemed ASP.NET vNext, the framework was going to be called ASP.NET 5 when ready. However, in order to avoid implying it is an update to the existing ASP.NET framework, Microsoft later changed the name to ASP.NET Core at the 1.0 release.[18]


  • No-compile developer experience (i.e. compilation is continuous, so that the developer does not have to invoke the compilation command)
  • Modular framework distributed as NuGet packages
  • Cloud-optimized runtime (optimized for the internet)
  • Host-agnostic via Open Web Interface for .NET (OWIN) support[19][20] – runs in IIS or standalone
  • A unified story for building web UI and web APIs (i.e. both the same)
  • A cloud-ready environment-based configuration system
  • A lightweight and modular HTTP request pipeline
  • Build and run cross-platform ASP.NET Core apps on Windows, Mac, and Linux
  • Open-source and community-focused
  • Side-by-side app versioning when targeting .NET
  • In-built support for dependency injection
  • Enhanced Security compared to Asp.Net [21]


See also


  1. ^ "Announcing ASP.NET Core in .NET 8". .NET Blog. 2023-11-14. Retrieved 2023-11-19.
  2. ^ "ASP.NET Core license". GitHub. Retrieved 2021-09-29.
  3. ^ "Choose between ASP.NET 4.x and ASP.NET Core".
  4. ^ singh Satinder. "Introduction to ASP.NET Core". Retrieved 10 July 2017.
  5. ^ "Introduction to ASP.NET Core".
  6. ^ "[Discussion] Updated Blazor browser support for .NET 5 · Issue #26475 · dotnet/aspnetcore". GitHub. Retrieved 2020-11-11.
  7. ^ "GitHub - dotnet/core: Home repository of .NET and .NET Core". October 20, 2019 – via GitHub.
  8. ^ "ASP.NET Blog | Announcing ASP.NET Core 2.2, available today!". ASP.NET Blog. December 4, 2018.
  9. ^ a b c ".NET Core and .NET 5 official support policy". Microsoft. Retrieved 2019-12-06.
  10. ^ "ASP.NET Blog | ASP.NET Core and Blazor updates in .NET Core 3.0". ASP.NET Blog. September 23, 2019.
  11. ^ "ASP.NET Core updates in .NET Core 3.1". ASP.NET Blog. December 3, 2019.
  12. ^ dotnet/aspnetcore, .NET Platform, 2020-11-11, retrieved 2020-11-11
  13. ^ "Announcing ASP.NET Core in .NET 6". .NET Blog. 2021-11-08. Retrieved 2021-11-19.
  14. ^ ".NET and .NET Core Support Policy". Microsoft. Retrieved December 30, 2022.
  15. ^ "Announcing ASP.NET Core in .NET 7". .NET Blog. 2022-11-08. Retrieved 2022-11-08.
  16. ^ ".NET and .NET Core Support Policy". Microsoft. Retrieved November 19, 2023.
  17. ^ "Announcing ASP.NET Core in .NET 8". .NET Blog. 2022-11-08. Retrieved 2023-11-19.
  18. ^ Jeffrey T. Fritz. "ASP.NET 6 is dead - Introducing ASP.NET Core 1.0 and .NET Core 1.0". .NET Web Development and Tools Blog. Retrieved 20 January 2016.
  19. ^ "OWIN". ASP.NET 0.0.1 documentation.
  20. ^ "Roadmap". Github.
  21. ^ "ASP.NET vs ASP.NE CORE". ASP.NET VS. ASP.NET Core: The Ultimate Showdown.

External links