SDK 2.1.100 installed after updating VS 2017 15.6.1

@Vaiune commented on Fri Mar 09 2018

I’ve updated visual studio 2017 to 15.6.1 this morning. After that i got

.NET Command Line Tools (2.1.100)

Product Information:
 Version:            2.1.100
 Commit SHA-1 hash:  b9e74c6520

Runtime Environment:
 OS Name:     Windows
 OS Version:  6.1.7601
 OS Platform: Windows
 RID:         win7-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.1.100\

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.5
  Build    : 17373eb129b3b05aa18ece963f8795d65ef8ea54

Prior to update I had 2.1.4 and everything was fine. dotnet new react scaffolds the old template that doesn’t use create-react-app as it should. If I create a global.json file indicating SDK 2.1.4 then it scaffolds the correct template with CRA.

https://www.microsoft.com/net/download/Windows/build shows 2.1.4 as the latest version.

Is this supposed to happen with the update VS 2017 15.6.1?

---

@Kritner commented on Fri Mar 09 2018

Ok, so not just me!

I see that I do in fact have 2.1.4 in my sdks folder, but even at root, with no global.json config, dotnet --version shows 2.1.100.

I unfortunately cannot confirm that it said 2.1.4 prior to the VS update.

[livarcocc]

SDK 2.1.102 does not include .NET Core 2.1. The earliest version available of teh .NET Core SDK that is compatible with .NET Core 2.1 is 2.1.300 which is available as preview1 at get.dot.net.

We have since then re-worked our versioning story to align the SDK version major.minor version numbers with the runtime major.minor version numbers, but until we are past 2.1, we will have this confusion point.

[Kritner]

huh… maybe that’s just my misunderstanding of versioning (is this semantec versioning?). I was under the impression the trailing zeroes were ignored (similar to a decimal), but I can’t actually find any information on it.