|
|
|
|
|
by runesoerensen
227 days ago
|
|
Might be more confusing when you consider that ".NET 5" is actually the continuation of ".NET Core 3.1", not ".NET Framework 4.x"[0]. Microsoft has historically been pretty bad at naming stuff (sometimes hilariously so, see Microsoft PlaysForSure[1] for an example - spoiler: it surely didn't play for long). The rebranding from .NET Core 3.1 to .NET 5, and from .NET 4.x to .NET Framework, did make sense to me though - and increasingly so as development continues on ".NET > 5" with yearly releases, while ".NET Framework 4.x" is in maintenance mode. [0]:https://learn.microsoft.com/en-us/dotnet/core/whats-new/dotn... [1]:https://en.wikipedia.org/wiki/Microsoft_PlaysForSure |
|