Skip Navigation
.NET @programming.dev πŸ’‘πš‚π—†π–Ίπ—‹π—π—†π–Ίπ—‡ π™°π—‰π—‰π—ŒπŸ“± @programming.dev

.NET Terminology

blog.lhotka.net .NET Terminology

I was recently part of a conversation thread online, which reinforced the naming confusion that exists around the .NET (dotnet) ecosystem. I thought I’d summarize my responses to that thread, as it surely can be confusing to a newcomer, or even someone who blinked and missed a bit of time, as things...

Maybe something to add to the side-bar?

5

You're viewing a single thread.

5 comments

  • Maybe something to add to the side-bar?

    The linked post doesn't seem like that good of a reference that I would put it in the sidebar. IMO it could be done better. But if you mean to say, something like it; yeah, the .NET environment is vast and can be confusing, especially when new to it. An overview or reference to one makes sense.

    I suppose the term β€œ.NET” encompasses both, but most of us that write and speak in this space tend to use β€œ.NET Framework” for legacy, and β€œ.NET” for modern .NET.

    there’s the whole β€œ.NET Core” thing

    Before around net7, the open source cross platform non-framework dotnet was called Core. net6/7/8 is the .NET Core technology, but Core was dropped from the naming.

    Now, .NET may refer to that modern dotnet tech, or .NET Framework. Presumably, the latter is referred to only in contexts where it's obvious that .NET Framework is meant.

    and .NET Standard (2 versions). […] Are those relevant in the world right now, today? Hopefully not really!

    .NET Standard is still relevant for libraries that target/publish for both .NET Framework and net6+. .NET Standard is the cross-platform baseline.