Closed deanchalk closed 1 year ago
Any update one this ? It seems that XMAL Islands is now completely broken
OK, seems like Im trying to setup XAML Islands in a WPF app that targets .net 5 - which Ive just read as being unsupported. I will therefore close this issue
Actually, Ive just tried with a WPF app that targets ,Net core 3.1, and the issue is still there
@Austin-Lamb and @JesseCol FYI
Adding @marb2000
@deanchalk can you create a app manifest in your WPF app? The toolchain requires a manifest to adding automatically some attributes. If this doesn't work, you can follow this guideline: https://techcommunity.microsoft.com/t5/windows-dev-appconsult/using-xaml-islands-on-windows-10-19h1-fixing-the-quot/ba-p/376330 Let me know of this helps.
Adding an app manifest or a packaging project didn't work, but thanks for the suggestion. It seems like XAML islands are no longer something that works, as these are all new projects following a Microsoft tutorial - it doesn't get any simpler than that. I need to move onto something else, so ill try again after the next release to see if its been fixed
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 5 days.
Describe the bug
After following exactly this tutorial: https://docs.microsoft.com/en-us/windows/apps/desktop/modernize/host-custom-control-with-xaml-islands I get an error 'The process has no package identity. (0x80073D54)'. This error occurs in the UWP App (Initialize()) that runs with the WPF app.
If I don't add the Microsoft.UI.XAML nuget to the solution, and use standard controls instead it works fine
Steps to reproduce the bug
Create a solution that uses XAML Islands and the Toolkit, as per the Microsoft tutorial above
Expected behavior I expect the solution to run without issues
Screenshots
Version Info 2.6.0-prerelease.210113001
Additional context