3 ms·
You’re not alone. I would say I’m not ‘new’ and even developed .net 4.5 for a number of years. I’m just as stumped by the naming mess that Microsoft made acros
by hsbauauvhabzb 2y ago
You’re not alone.
I would say I’m not ‘new’ and even developed .net 4.5 for a number of years. I’m just as stumped by the naming mess that Microsoft made across the board in that space.
Edit: I say 4.5 because I mean the original thick .net which is not dotnet core, which I think is the way to differentiate between versions, but also all the sub libraries like the orm were iirc named the same but did different things.
They should have rebadged everything with a new name that didn’t involve a word that is fairly painful to google (‘core’) can be used in development as well as the name of a framework.
- shiroiushi 2y agoI think Microsoft is completely allergic to naming anything with a unique name or term; in fact, it's almost like they pick names that will be hardest to find with a google search.
- notakio 2y agoThis is compounded by their propensity to rename everything at periodic intervals.
- drw85 2y agoIt's even worse, since they dropped the core now and just call it .NET. So searching has become even more of a pain. It's also pretty much a mess, because many things were different between the versions. So let's say you google how to do something and the result could be: - .NET Framework - .NET core 1 - .NET core 2 - .NET core 2.1 - .NET core 3 - .NET 5+ Many times there will be no clear indication what version the result was built on. On stackoverflow, answers sometimes include all versions varieties.
- neonsunset 2y agoGiven current naming scheme, what do you propose?