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.

Update URL for dotnet-core-preview

See original GitHub issue

When creating a project with a preview SDK, the following message is printed:

  You are using a preview version of .NET. See: https://aka.ms/dotnet-core-preview

Given that we’re no longer branding as “.NET Core”, we should update that URL.

Issue Analytics

State:
Created 2 years ago
Comments:16 (14 by maintainers)

Top GitHub Comments

1reaction

baronfelcommented, Jan 6, 2022

@marcpopMSFT https://aka.ms/dotnet-support-policy has been created to serve as the target for this work.

1reaction

terrajobstcommented, May 6, 2021

I agree with Rich, the warnings for SDK previews seem of low value to me. Also, the SDK is something that the developer of the machine controls which is different from the what the projects themselves are targeting because build can transparently acquire targeting packs.

Scenarios:

I install a supported version of the .NET SDK (say, .NET 5 today). I then git clone some repo that happens to target .NET Core 3.0. I get a warning that .NET Core 3.0 is out of support. That makes sense to me.
I install a preview version of .NET 6.0 SDK. I build my .NET 5 app. I get multiple warnings (one per project) that I’m using a preview version of the .NET SDK. Duh, I downloaded that one for a reason. This doesn’t make sense to me.