-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Include all required shims when building in VMR #61282
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
Include all required shims when building in VMR #61282
Conversation
| <!-- Use the same NETCore shared framework as repo built against except when building product code in servicing. --> | ||
| <KnownFrameworkReference Update="Microsoft.NETCore.App"> | ||
| <!-- We cannot use live shims when building tool packs in VMR - only package for current arch is available. --> | ||
| <KnownFrameworkReference Update="Microsoft.NETCore.App" Condition=" '$(DotNetBuild)' != 'true' OR '$(PackAsToolShimRuntimeIdentifiers)' == '' "> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To confirm, PackAsToolShimRuntimeIdentifiers is usually empty, right? Because we always want to update this, except for in these tool package scenarios in the VMR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, PackAsToolShimRuntimeIdentifiers is not set (i.e. empty) unless a specific project builds as a tool and needs to pack shims.
wtgodbe
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM other than the 1 question
Contributes to dotnet/source-build#4944
We don't have all live shims when building in VMR. The fix is to restore shared framework and apphost packs and not use the live ones, as only one architecture is available.