Re:How Async/Await Works in C#
by SideburnsOfDoom on Saturday March 18, 2023 @01:20PM
(#35211053)
> 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?
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.
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.