-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Various fixes in Microsoft.NETCore.App packs #45566
Conversation
…shared with the libraries area.
cc: @JunTaoLuo |
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, but I don't fully understand it.
<PlatformManifestFileEntry Include="netstandard.dll" /> | ||
<PlatformManifestFileEntry Include="WindowsBase.dll" /> | ||
<PlatformManifestFileEntry Include="Microsoft.VisualBasic.dll" /> | ||
<PlatformManifestFileEntry Include="System.ComponentModel.DataAnnotations.dll" /> |
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.
You can actually drive these off https://github.com/dotnet/runtime/blob/master/src/libraries/shims/netfxreference.props
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.
This is OK to go as is. Consider a follow up to reduce the list using netfxreference.props.
Include the fallback RID graph in the Microsoft.NETCore.App runtime pack.
Remove extraneous entries from the Microsoft.NETCore.App platform manifest and drive generation of the platform manifest entries for managed libraries from a list that already exists in the libraries portion of the repo.