Skip to content

Conversation

@AmadeusW
Copy link
Contributor

@AmadeusW AmadeusW commented Feb 7, 2018

The hard link in the error message points to a specific version of .NET SDK installer which causes user's machine to end up in a bad state: see dotnet/cli/issues/8531 and this

This PR changes the link to the general download page, where user may get a correct and supported version of the SDK

Ask Mode template not completed

Customer scenario

What does the customer do to get into this situation, and why do we think this
is common enough to address for this release. (Granted, sometimes this will be
obvious "Open project, VS crashes" but in general, I need to understand how
common a scenario is)

Bugs this fixes

(either VSO or GitHub links)

Workarounds, if any

Also, why we think they are insufficient for RC vs. RC2, RC3, or RTW

Risk

This is generally a measure our how central the affected code is to adjacent
scenarios and thus how likely your fix is to destabilize a broader area of code

Performance impact

(with a brief justification for that assessment (e.g. "Low perf impact because no extra allocations/no complexity changes" vs. "Low")

Is this a regression from a previous update?

Root cause analysis

How did we miss it? What tests are we adding to guard against it in the future?

How was the bug found?

(E.g. customer reported it vs. ad hoc testing)

Test documentation updated?

If this is a new non-compiler feature or a significant improvement to an existing feature, update https://github.com/dotnet/roslyn/wiki/Manual-Testing once you know which release it is targeting.

The hard link points to a specific version of .NET SDK installer which causes user's machine to end up in a bad state: see [dotnet/cli/issues/8531] and [this](dotnet/designs#29 (comment))

This PR changes the link to the general download page, where user will get a correct and supported version of the SDK
@AmadeusW AmadeusW requested a review from a team as a code owner February 7, 2018 20:52
Copy link
Member

@jaredpar jaredpar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have an issue open to update our CLI version. Until then we need to keep pointing to this build as it has features needed to build our repo.

Copy link
Contributor

@sharwell sharwell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This error message was the only way we were able to figure out how to unblock testing of #24673. Until the specific version requirement is removed, this error message needs to always point at the specific installer required for building this repository.

@sharwell
Copy link
Contributor

@jaredpar I wanted to close this in favor of the issue you mentioned, but was unable to find it.

@jaredpar
Copy link
Member

Here is the tracking issue #24591

I have to wait for a broader announcement to come through before I can fix that issue. Once it's out though I will pretty quickly get it fixed.

@jaredpar jaredpar closed this Feb 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants