Hacker News Reader

Comment by gardenhedge | Hacker News Reader

Is it not currently asp.net core?

.NET is kind of like JVM but also usually includes an SDK, a build system and a package manager (NuGet), when people use the term.

It is then targeted by various languages: C#, F#, VB.NET and smaller projects - anything that emits "canonical" .NET assemblies (that use IL) works.

ASP.NET Core is a web framework for .NET, it's distributed with SDK so "comes out of box".

EF Core is an ORM framework, it does not come out of box and can be added as nuget packages (the dependency itself and then specific DB driver).

> ASP.NET Core is a web framework for .NET

ASP.NET Core is not a web framework for .NET; it's at least four different web frameworks you can choose between. It's more like the overarching branding for anything web-related in the dotnet ecosystem.

https://learn.microsoft.com/en-us/aspnet/core/tutorials/choo...

Kind of?

All these, effectively, plug into ASP.NET Core, on top of WebApplicationBuilder and WebApplication. They are then, usually, hosted with Kestrel (web server) and operate with the same set of abstractions. Razor Pages and Blazor are distinct names and I have never seen anyone confuse them with the ASP.NET Core itself.

ASP is an odd name to an old hat like me. Active Server Pages haven't been a thing in a while.

You see, this is where it gets confusing. ASP refers to a specific technology, active server pages, but it's also the overarching term used for anything to do with dotnet and the web. So you get this: https://learn.microsoft.com/en-us/aspnet/core/tutorials/choo... - you can have an entirely frontend SPA, in at least two ways, and still be called "ASP.NET"

I have an application which only serves over GRPC. It has to pull in "Asp.Net" nuget packages, because that's the branding under which the Kestrel HTTP2 server lives.

Yes, it's still called "ASP.NET Core", even though ".NET Core" was renamed ".NET" from version 5 -- not to be confused with ".NET Framework 5", which was renamed ".NET Core 1.0" before launch.

Don't forget ".NET Standard" that could be used from both .NET Core and .NET Framework, until version 2.1.

Reply on news.ycombinator.com