Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

.NET Core SDK 2.0.3 has hard-coded version string in bundle UI

See original GitHub issue

@barnson commented on Thu Nov 16 2017

Steps to reproduce

Install dotnet-sdk-2.0.3-win-x64.exe, downloaded from https://www.microsoft.com/net/download/windows.

Expected behavior

The Success page tells me I installed version 2.0.3.

Actual behavior

The loc string FirstTimeWelcomeMessage used on the Success page in the bundle has hard-coded 2.0.0 strings.

Environment data

n/a

Issue Analytics

State:
Created 6 years ago
Comments:27 (15 by maintainers)

Top GitHub Comments

1reaction

pokecommented, Jan 10, 2018

@KathleenDollard

So I suggest we

fix this now by updating the version numbers that were already there (runtime and SDK), and

create a new issue to establish the right way to communicate the contents of each SDK.

I agree with this plan. The original list of installed components is good enough for the installer. As @dasMulli said, those are the things that actually get installed and what I should be conscious about. The internal components are interesting from a debugging perspective but serve no real use while installing.

So if the SDK installer contains the .NET Core SDK, the .NET Core Runtime, and the Runtime Package Store, then those should list their actual version numbers.

Then, I would like to see dotnet --info expanded to include the full details about the individual components (e.g. MSBuild, NuGet, Roslyn), so that as a developer, I can easily see what versions of those things I am using when I do stuff.

In addition, I think it would be very helpful to have some resource online to see exactly which SDK version includes what versions of those bits. So that when someone refers to a specific SDK version, I have a way to look up what versions are involved (e.g. to see whether specific Roslyn features are available). As an example, I was directed to this issue because of a discussion where we wanted to figure out what SDK version is the earliest to support a certain C# version. By being able to look up what Rosyln versions ship with each released SDK, this would have been a lot easier.

1reaction

Petermarcucommented, Dec 14, 2017

Yes, you can set <RuntimeFrameworkVersion>2.0.3</RuntimeFrameworkVersion> in your project or pass /P:RuntimeFrameworkVersion=2.0.3 on the command line to publish and it should pick up 2.0.3.

Top Results From Across the Web

NET Core SDK 2.0.3 has hard-coded version string in bundle UI

The loc string FirstTimeWelcomeMessage used on the Success page in the bundle has hard-coded 2.0.0 strings. Environment data. n/a.

Select which .NET version to use

NET CLI must choose an SDK version for every dotnet command. It uses the latest SDK installed on the machine by default, even...

VSTS dotnet Nuget Pack: Is not a valid version string

The pack fails with the error BuildName_2018.7.11.1-beta is not a valid version string . I have previously used this environment variable as my ......

Overview of the Google Play Core libraries

This page describes the Google Play Core libraries and how to add them to your project. Important: The Google Play Core Java and...

Activities - Release notes

Release notes. To learn what has changed, check out the release notes. ... Activities package version 1.9.5 to be incompatible with UI Automation....