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

Fix merged component support in non-WinRT component projects #1680

Merged
merged 1 commit into from
Jul 31, 2024

Conversation

Sergio0694
Copy link
Member

This PR adds support for generating WinRT exports to chain referenced components, from non-component projects.

@Sergio0694 Sergio0694 added authoring Related to authoring feature work AOT labels Jul 24, 2024
@jevansaks
Copy link
Member

One issue is that we still need the merged winmd written to the output location. That's done in the authoring targets via CsWinRTPlaceWinMDInOutputFolder. We need an equivalent thing for projects that set CsWinRTMergeReferencedActivationFactories=true but not CsWinRTComponent=true.

@Sergio0694
Copy link
Member Author

Is that not a separate feature? I mean one can also just copy all the individual .winmd-s to the output and just indicate the merged .dll as the implementation .dll for all of those .winmd-s, right? Eg. UWP currently does that, there's no single merged .winmd.

@jevansaks
Copy link
Member

I'm ok with getting this fix and just documenting that it does only thing and you might have to do some other targets work yourself.

@Sergio0694 Sergio0694 force-pushed the user/sergiopedri/improve-merged-components branch from 21202e3 to 6f43f03 Compare July 30, 2024 21:13
@Sergio0694 Sergio0694 merged commit eb3b9c3 into staging/AOT Jul 31, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AOT authoring Related to authoring feature work
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants