It all started with '.NET Framework', which was the old Windows-only implementation. Eventually they rewrote everything to be cross-platform and called it '.NET Core'.
Distinguishing between the two was confusing, so MS took the genius decision of rebranding it all as just '.NET'. So today you can make a project in .NET 5, .NET 6, .NET 7, etc., and they're all cross-plat.
Various frameworks exist on top of .NET. The biggest one is ASP.NET Core, the web framework. And there's frameworks on top of that like Blazor.
The runtime is JIT by default, but you do actually have AOT options nowadays, which is nice.
The JRE-equivalent in the .NET stack is the Common Language Runtime. The JRE processes Java bytecode; the CLR processes Common Intermediate Language (CIL, formerly MSIL) instructions.
Even those the work at Microsoft haven't been able to work that out since they coined the term, let alone developers etc.
an ecosystem made of languages, compilers, runtimes, libraries, tools and community.
.NET Framework is analogous to the JVM.
Micro-frameworks that don’t pack the kitchen sink like nodejs became popular, so Microsoft made .NET Core to be philosophically similar to that.
Because people such as yourself got confused by this, they eventually stopped pushing Framework and renamed .NET Core to .NET.
Microsoft has never been popular with the valley crowd, so everything they have ever done is pooped on constantly by people on here.
You should check out some of the posts on here when VS Code came out. A lot of people were amazed that Microsoft had built something decent “out of nowhere” like those people hadn’t just been living in a bubble their whole career.
Wouldn't CLR be closer to JVM? https://learn.microsoft.com/en-us/dotnet/standard/clr
And then... I don't know, .NET Framework to JDK, or something like that?
I like the whole thing (since .NET now runs on Linux well enough, C# feels okay as a language and has good tooling, like Visual Studio or JetBrains Rider) but there's definitely some naming and branding confusion sometimes going on, including in my own head.
No, its the library, not the runtime.
> Micro-frameworks that don’t pack the kitchen sink like nodejs became popular, so Microsoft made .NET Core to be philosophically similar to that.
.NET Core was still a very batteries-included library, it just dumped bits tied to Windows and made some other backward-compatibility sacrifices to get something cross platform and open sourcable.
> Because people such as yourself got confused by this, they eventually stopped pushing Framework and renamed .NET Core to .NET.
IIRC, they announced the long term plan to move all functionality that would be retained into Core and converge on a single implementation fairly early on, but to move forward in parallel until then .NET Standard versions were created to identify compatibility across Core and Framework during this period.) Dropping Framework and making Core just unqualified . NET (and eliminating the need for Standard) was just the completion of that strategy.
Except you don't need anything .Net specific to be installed on the end user machine. I build and deploy single-file C# binaries to Linux all the time. There's no longer a dependency on having the .Net framework installed or having dozens of DLLs accompanying your binary.
This is an orthogonal concern to running on Linux, Which could depend on a shared runtime, or not.
Which does .NET do? all of the above.
This is not wrong.
.NET Framework = the built-in class libraries. Confusingly, also .NET Framework can mean the older, legacy, Windows only version of the whole thing.
NuGet = package management for built-in and 3rd party libraries.
Roslyn = the C# compiler
MSIL: the bytecode "Intermediate Language" emitted by that compiler
CLR = Common Language Runtime for MSIL, and related concerns such as GC and JIT
C# a general purpose language, OO-first but with some functional things.
The other problem is that it's broad: a person can use C# and.NET for one thing (e.g. Web services, or Desktop GUIs), and have strong opinions about what's needed and how to do things, and assume that this is universal but ... it isn't true of the other.
Yeah, it's confusing. Took me some work to get through too.
It’s not .NET Framework anymore. Or .NET Core. And it’s none of the countless random things Microsoft has labelled .NET. I think the name fundamentally misleads my brain every time given it’s not necessarily a web framework. I need .NET runtimes for my video games.
So it’s basically a managed group of tools and libraries to let you build stuff in a handful of different languages, usually C#, but targeting the same runtime, which is a JIT? So is it basically like Java but with far too much marketing involvement over the years?