5 ms·
>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 curr
by rubber_duck 10y ago
>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