-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Different RID behavior for multitargeted restore in VS and command line #871
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
Comments
Looks like |
@dasMulli Yes. Just hit this and it was also running too late. Using BeforeTargets="_GenerateRestoreProjectSpec" fixes both issues. |
btw, I think this would help a lot when using native dependencies for library projects that target full fx + specific RID and netstandard. (https://github.com/dotnet/cli/issues/5241, https://github.com/dotnet/cli/issues/5241#issuecomment-271392503) |
…812.1 (dotnet#871) - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19412.1
Uh oh!
There was an error while loading. Please reload this page.
If
RuntimeIdentifer(s)
differ between inner builds, then VS will gather the properties from each inner build and send them on to restore whereas the command line restore target only reads them from the outer evaluation context.Repro project
Behavior in VS (and expected behavior)
Builds successfully
Behavior on command line (dotnet restore; dotnet build)
(and other related errors)
@emgarten @srivatsn @natidea This is causing issues for #847 in multi-targeted app case. I think the right fix would be in nuget restore targets to gather all RIDs from inner builds, but I think I can do that in SDK with a BeforeTargets="Restore"
The text was updated successfully, but these errors were encountered: