Comment by jsingleton | Hacker News Reader

Comment by jsingleton | Hacker News Reader

I wonder if there is some confusion between .NET Standard and .NET Core. As .NET Standard 2.0 is a thing but I can't find any official reference to .NET Core 2 yet. Obvious, this will eventually come but it's not on the roadmap yet as far as I can see.

https://github.com/aspnet/home/wiki/roadmap

https://blogs.msdn.microsoft.com/dotnet/2016/07/15/net-core-...

Disclaimer: I've not been paying as close attention as I did last year when writing my book on .NET Core (https://unop.uk/book/). So I may just have missed something.

Edit:

I've found some more info: https://github.com/dotnet/core/blob/master/roadmap.md#ship-d...

  Milestone 	 	Release Date
  .NET Core 2.0 	Spring 2017
  .NET Standard 2.0 	Spring 2017

This is weird as I had previously heard this would be v1.2. Perhaps it is but it's now a major bump rather than a minor one. Either a breaking change or to tie in with .NET Standard?

I guess this means it won't stay aligned with the ASP.NET Core versions now?

I spend time writing a helpful comment and the thread gets flagged. :(

From the roadmap: "Because of this, if you follow our repositories you will start to see .NET Core 2.0 versioning."[0]

As an aside, I find it helpful to think of .net standard as an interface (API definition, no code), and .net core as a class (implements interface, provides implementation, possibly additional methods).

  public class NetCore2_0 : INetStandard2_0 {}

  public class NetCore1_0 : INetStandard1_6 {}

[0] - https://github.com/dotnet/core/blob/master/roadmap.md

.NET Core 1.2 is now 2.0 so that it aligns with .NET Standard and reduces confusion (of which there is too much already and the worst part of .NET in general).

This is a good reference: https://docs.microsoft.com/en-us/dotnet/articles/standard/li...

Just replace .NET Core vNext with 2.0 and you're looking at the latest mapping of .NET Standard implementations.

>Either a breaking change or to tie in with .NET Standard?

Maybe they just want to sync with .NET core tools which have a breaking change even if they are currently RC - just moving everything to 2.0 would signal that everything is in sync now - hopefully.

They need a major version re-release, 1.0 was premature for the way it was done, hoping they get things right with 2.0

I think its all bumping to 2.0 as the versions were becoming crazily unaligned and the installer showed about 4 version numbers.

No doubt they my become unaligned again in the future; but I think its about starting from a clean version number alignment.

e.g. .NET Standard 2.0 was originally .NET Standard 1.7 which would have gone with .NET Core 1.2 with tooling (CLI) 1.0

Reply on news.ycombinator.com