-
Notifications
You must be signed in to change notification settings - Fork 698
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
Microsoft.UI.Xaml.winmd not included in build output #4701
Comments
@ollitanska Thanks for the bug! do you have a repro app you could provide here? it would be handy in fixing this :) |
@ranjeshj I think this is needed for 2.6 release. |
Here is a minimal repro app. |
Hi @ollitanska - I have a candidate fix that works on my side, but I was hoping you could test it out and see if it works for you as well before I send it out for PR. Could you put this at the very bottom of App1.csproj, just before
If this does work for you, also try it in whatever app you were using where you found this. If it works in both locations, I can get this fix in the pipeline. |
Works great, both on the repro app and our real app! Thanks for quick response! |
Sweet, thanks for the confirmation! I'll get that out for PR. |
Is it possible to add an option to not copy the file still, since C++ based Xaml islands apps don't need the winmd. |
A recent change I made worked around a .NET Native issue by having us no longer copy the WinMD file to the output directory, but that broke unpackaged XAML islands apps since they rely on it being there. I've added a line to the targets file to copy the WinMD once .NET Native compilation has completed, which fixes the issue. This did, however, surface the fact that we don't currently have any XAML islands coverage in our CI pipeline. To fix that, I've added a WPF application and have a canary test that launches the application in both a packaged and an unpackaged state, and retrieves and clicks a button, just to ensure that both forms of XAML islands apps launch correctly. Fixes #4701
Describe the bug
After upgrading to v2.6.0-prerelease.210315002 from v2.6.0-prerelease.210227001, the Microsoft.UI.Xaml.winmd is not included in the output directory anymore. Microsoft.UI.Xaml.dll and Microsoft.UI.Xaml.pri are included as expected.
This causes the following exception when starting up the application: 'System.TypeLoadException: Could not find Windows Runtime type 'Microsoft.UI.Xaml.Controls.XamlControlsResources'.
This regression seems to be caused by this commit: #4218
Steps to reproduce the bug
Expected behavior
Application would startup normally, Microsoft.UI.Xaml.winmd would be included in the output directory.
Version Info
NuGet package version:
[Microsoft.UI.Xaml.v2.6.0-prerelease.210315002]
Additional context
WPF application that hosts a custom UWP control (which uses WinUI 2.6) via XAML Islands.
The text was updated successfully, but these errors were encountered: