-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update 16.7 error message when targeting 5.0 #5820
Comments
@benvillalobos mind prepping a 16.7 fix for this? No rush as we have a week or so before they lock down. Talk to Kathleen about the specific message to show and talk to Rainer about the app types he's concerned about. Test 5.0-windows. |
Sure. What is the expected value of |
Created PR for the rest of the discussion here: #5826 |
@marcpopMSFT Targeting net5.0-windows results in an SDK error:
|
That seems like a reasonable message. I don't think we want to try to special case every possible targetframework that we don't recognize. @KathleenDollard as an FYI. |
Any reason this is still open? |
@Forgind I'll keep this open until we also merge into |
May want to test if this makes sense in 16.8 as it may not apply after 16.7. |
Still gives an error on |
@mc0re do you have a global.json file that's lowering the sdk you use while targeting your app to net5.0? |
The error gone away after updating to 16.9.2. Now I have other problems, but they are more click-once related :-) |
Issue
If a customer created a net 5 app or got one from a coworker, opens it in 16.7, we have a bad error experience today as we decide it must be a framework application.
dotnet/core#5311
We don’t recognize the TFM so we assume it’s a .net framework version and the message matches that.
Proposal
Update MSBuild 16.7 with a new message in this specific scenario in the below code path.
@rainersigwald, any concerns just adding a check here for if the version is >= to 5.0 and providing a different error? That seems like the narrowest way to solve this with the least risk. I wouldn’t bother with 16.4.
msbuild/src/Tasks/GetReferenceAssemblyPaths.cs
Line 249 in 2966524
Other questions
The text was updated successfully, but these errors were encountered: