ASP.NET is like ML.NET an Framework on top of .NET.
There are two different versions "ASP.NET Core" and "ASP.NET". The first one only runs on .NET core (windows, Linux, etc. ) and the latter only on .NET Framework (Windows only).
ASP.NET is the Server framework for .NET Framework.
It is a collection of assemblies providing you with a set of APIs to build your web pages.There is ASP.NET WebForms and ASP.NET MVC, both are depending on an IIS.
As @Niels already mentioned, there are two flavors of ASP.NET.
ASP.NET (as described above) and ASP.NET Core, which works a bit differently.
For ones, Core comes without the need for an IIS, although you can use it with an IIS. As a second, it does no longer support WebForms (I never liked those) but comes with MVC, Razor Pages, Server side Blazor and Client side Blazor (WebAssembly since 3.1), which all work a bit differently, allowing you to look for the best fit for your needs and style.
Thanks, Andreas! Could you please expand on how ASP.NET fits into it all?
ASP.NET is like ML.NET an Framework on top of .NET.
There are two different versions "ASP.NET Core" and "ASP.NET". The first one only runs on .NET core (windows, Linux, etc. ) and the latter only on .NET Framework (Windows only).
Thank, Niels!
ASP.NET is the Server framework for .NET Framework.
It is a collection of assemblies providing you with a set of APIs to build your web pages.There is ASP.NET WebForms and ASP.NET MVC, both are depending on an IIS.
As @Niels already mentioned, there are two flavors of ASP.NET.
ASP.NET (as described above) and ASP.NET Core, which works a bit differently.
For ones, Core comes without the need for an IIS, although you can use it with an IIS. As a second, it does no longer support WebForms (I never liked those) but comes with MVC, Razor Pages, Server side Blazor and Client side Blazor (WebAssembly since 3.1), which all work a bit differently, allowing you to look for the best fit for your needs and style.
Thank you :)