Skip to content
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

Fixed removal of dll references that report IsWinmdFile == true #533

Merged
merged 2 commits into from
Oct 21, 2020

Conversation

Scottj1s
Copy link
Member

@Scottj1s Scottj1s commented Oct 21, 2020

Some references required by csc are inadvertently removed because they record true for being WinMD files, but actually have a DLL extension.

@Scottj1s Scottj1s merged commit af63025 into master Oct 21, 2020
@Scottj1s Scottj1s deleted the scottj1s/dll_with_winmd branch October 21, 2020 21:23
@@ -27,11 +27,11 @@ Copyright (C) Microsoft Corporation. All rights reserved.
<Target Name="CsWinRTRemoveWinMDReferences" BeforeTargets="ResolveReferences;BeforeCompile" AfterTargets="AfterResolveReferences">
<ItemGroup>
<!--Move winmd references into private item group to prevent subsequent winmd reference errors-->
<CsWinRTRemovedReferences Include="@(ReferencePath)" Condition="'%(ReferencePath.WinMDFile)' == 'true'" />
<CsWinRTRemovedReferences Include="@(ReferencePath)" Condition="'%(ReferencePath.Extension)' == '.winmd'" />
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is ReferencePath an object with fields WinMDFile and Extension? Or did you change the WinMDFile field to Extension?

@AdamBraden
Copy link
Contributor

Not sure I understand the root issue - dlls were getting marked IsWinMDFile=true. Who is doing this, are they winmd files with the wrong extension? If they are not winmd files, doesn't that point to a VS or Net5 problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants