ASP.NET 5 is dead – Introducing ASP.NET Core 1.0 and .NET Core 1.0

Re:ASP.NET 5 is dead – Introducing ASP.NET Core 1.0 and .NET... by RachelF on Wednesday January 20, 2016 @05:02AM (#10937016)

Indeed, way too confusing.

".NET Core 5 is now .NET Core 1.0. " Really? What happens when .NET Core v 2.0 comes out?

.NET is drowning in a confusion of its own making.

[ Parent | on HN ]

Re:ASP.NET 5 is dead – Introducing ASP.NET Core 1.0 and .NET... by taspeotis on Wednesday January 20, 2016 @05:06AM (#10937032)

> ".NET Core 5 is now .NET Core 1.0. " Really? What happens when .NET Core v 2.0 comes out?

Is your point that v2 ... v3 ... v4 will eventually overlap with .NET Core 5? Because .NET Core 5 hasn't actually been released yet.

[ Parent | on HN ]

Re:ASP.NET 5 is dead – Introducing ASP.NET Core 1.0 and .NET... by cm2187 on Wednesday January 20, 2016 @06:57AM (#10937462)

I think it's worse. When you will be googling a question for .Net core 2.0, you will find responses for .Net 2.0. But .Net core is not backward compatible, they removed lots of stuff. We would have been better off if they had called it "Monkey 1.0" instead of ".Net Core 1.0".

[ Parent | on HN ]

Re:ASP.NET 5 is dead – Introducing ASP.NET Core 1.0 and .NET... by khellang on Wednesday January 20, 2016 @07:02AM (#10937483)

Even if it had shipped, what's stopping them from skipping 5 and "turn it up to 6"? ;)

[ Parent | on HN ]