-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Building for desktop shouldn't require a RID #730
Comments
Dupe of dotnet/project-system#1333. |
That's fair, but the targets live here so I thought this would be the place to file the issue. https://github.com/dotnet/sdk/blob/master/src/Tasks/Microsoft.NET.Build.Tasks/build/Microsoft.NET.RuntimeIdentifierInference.targets |
Both are dupes to another issue in the SDK - #357 :) |
Thanks @srivatsn |
Ha, and that one is a dup of #396 |
mmitche
pushed a commit
to mmitche/sdk
that referenced
this issue
Jun 5, 2020
…262-bac8-b3ef94ce2a99 [master] Update dependencies from dotnet/arcade
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I build for desktop I see
Why do we force folks to specify a RID? We should be able to restore and build just fine without a RID for desktop. That's the precedent set by NuGet 2. At the very least we should probably be just assuming some RID for desktop if the user hasn't specified one. Forcing it in the project file is busted.
The text was updated successfully, but these errors were encountered: