NETSDK1045 Error is just going to docs.microsoft.com

[dougboone5]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[welcome]

Thank you for creating the issue! One of our team members will get back to you shortly with additional information.

[dougboone5]

NETSDK1045 Error just goes to docs.microsoft.com root. Absolutely no help. How do you fix the error? I've done a search and replace across all the files in the solution (SignalR master) to get rid of all reference to .NET Core 3.0 but still get 62 errors. How about linking to a real error page?

Severity Code Description Project File Line Suppression State

Error NETSDK1045 The current .NET SDK does not support targeting .NET Core 3.0. Either target .NET Core 2.2 or lower, or use a version of the .NET SDK that supports .NET Core 3.0. Microsoft.AspNetCore.SignalR.StackExchangeRedis C:\Program Files\dotnet\sdk\2.2.201\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.TargetFrameworkInference.targets 137

VS 2019 RC, .NET Core 2.2.1 installed

[svick]

I can't comment on the issue with the link, but if you're trying to compile a project that requires a certain version of the .Net SDK, you should install that version of the SDK. Even if you managed to replace all direct references to .Net Core 3.0, it's likely that they are there for a reason. In other words, the project almost certainly uses APIs that only exist in .Net Core 3.0.

[mairaw]

@dougboone5 Is there a link you can share with us that perhaps the error is linking to before it redirects to docs.microsoft.com or does it go straight to docs? Maybe an aka.ms or fwlink?

[svick]

@mairaw I can reproduce this behavior. When I click on the NETSDK1045 error code in VS, the URL that opens is https://docs.microsoft.com/en-us/visualstudio/index?f1url=https%3A%2F%2Fmsdn.microsoft.com%2Fquery%2Fdev15.query%3FappId%3DDev15IDEF1%26l%3DEN-US%26k%3Dk(NETSDK1045)%26rd%3Dtrue%26f%3D255%26MSPPError%3D-2147217396&view=vs-2019.

Based on that url parameter, I think the URL initially opened by VS is https://msdn.microsoft.com/query/dev15.query?appId=Dev15IDEF1&l=EN-US&k=k(NETSDK1045)&rd=true&f=255&MSPPError=-2147217396, which seems like it's looking for documentation based on that error code and redirects to the documentation homepage for VS if it doesn't find anything.

I'm not sure what is the right thing to do here.

[mairaw]

Thanks @svick. I think we first need to determine where this should go. @KathleenDollard any suggestions for this NETSDK1045 error?
Then I think is just a matter of adding NETSDK1045 to the f1_keywords metadata in the desired topic.