undefined | Better HN

0 pointsSketchySeaBeast2y ago0 comments

I agree that's frustrating, but I doubt Microsoft will be able to ever outdo itself with its .NET Framework/.NET Core/.NET naming convention nonsense.

0 comments

giancarlostoro2y ago

.NET 7 and beyond consolidates Framework and Core. I think they're going to just stick to just .NET moving forward. Eventually Framework and Core will be EOL'd.

I do agree though, they did it very confusingly.

SketchySeaBeastOP2y ago

It's definitely better sorted now, but as a dev working in the .Net stack during the .Net 2.0 Core time, it was very confusing.

giancarlostoro2y ago

2.0? ;) I started with 1.0.1, which had very confusing versions like 1.0.1.1 and other weird nonsense... I wanted to scream at Microsoft.

RexM2y ago

Don’t forget .NET Standard.

Their naming for all of this is a disaster.

giancarlostoro2y ago

Standard was supposed to be the in-between for Framework and Core if I'm not mistaken, that will likely be phased out and EOL'd.

j / k navigate · click thread line to collapse

0 comments

giancarlostoro2y ago

.NET 7 and beyond consolidates Framework and Core. I think they're going to just stick to just .NET moving forward. Eventually Framework and Core will be EOL'd.

I do agree though, they did it very confusingly.

SketchySeaBeastOP2y ago

It's definitely better sorted now, but as a dev working in the .Net stack during the .Net 2.0 Core time, it was very confusing.

giancarlostoro2y ago

2.0? ;) I started with 1.0.1, which had very confusing versions like 1.0.1.1 and other weird nonsense... I wanted to scream at Microsoft.

RexM2y ago

Don’t forget .NET Standard.

Their naming for all of this is a disaster.

giancarlostoro2y ago

Standard was supposed to be the in-between for Framework and Core if I'm not mistaken, that will likely be phased out and EOL'd.

j / k navigate · click thread line to collapse