Update CLI Branding and Versioning

Update CLI version numbers and branding strings.

THIS IS A BREAKING CHANGE

Anyone testing with an older build of CLI may be broken by this change. The SDK version is moving from rc2 to preview1, a lower preview version string. Please uninstall/delete any older installation of dotnet prior to using a new version that includes this change.

Also note that folks depending on CLI-produced NuGet packages will be affected. Tools NuGet packages will also be affected. Anyone depending on 1.0.0-* version of CLI produced NuGet packages will need to include the updated version suffix e.g. 1.0.0-preview1-* to get the latest packages. See the table below for details.

Branding changes

• Microsoft .NET Core SDK --> Microsoft .NET Core 1.0 RC2 - SDK Preview 1
• Microsoft .NET Core --> Microsoft .NET Core 1.0 RC2 - Runtime
• Microsoft .NET Core Host --> Microsoft .NET Core 1.0 RC2 - Host

Versioning changes

The version update is less straightforward. The Shared Framework and its dependencies will remain RC2. The ProjectModel and its dependencies will also remain RC2. The remaining packages produced in this repo, namely the CLI and its dependencies, will have their version updated to preview1.

Component	Old Ver Suffix	New Ver Suffix
Host	rc2	rc2
Shared Framework	rc2	rc2
SDK	rc2	preview1
dotnet-compile-fsc.nupkg	rc2	preview1
Microsoft.DotNet.Cli.Utils.nupkg	rc2	preview1
Microsoft.DotNet.Compiler.Common	rc2	preview1
Microsoft.DotNet.Files	rc2	preview1
Microsoft.DotNet.InternalAbstractions	rc2	rc2
Microsoft.DotNet.ProjectModel	rc2	rc2
Microsoft.DotNet.ProjectModel.Loader	rc2	preview1
Microsoft.DotNet.ProjectModel.Workspaces	rc2	preview1
Microsoft.Extensions.DependencyModel	rc2	rc2
Microsoft.Extensions.Testing.Abstractions	rc2	preview1

[khellang]

Seriously? What’s the reasoning behind this?

[FransBouma]

A preview of the second release candidate. And not ‘the’ preview, but the first, so more will follow. Is this the equivalent of a beta of a release candidate? If so, perhaps you guys/gals should look up what the term ‘release candidate’ is used for 😉.

My suggestion would be to go back to beta -> RC1 -> RCn -> RTM and don’t change the world after Beta anymore, so trust in this release policy (if you can call it that) can be restored. I mean… what does ‘preview1’ even mean? Especially for people who want to start using coreFX when RC2 drops: do they have to wait till the preview days are over and RC2, the GA version that is of RC2, hits the streets? Confusing.