You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 25, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Feb 25, 2026. It is now read-only.
My ProjectPeunion solution is crashes, when I'm trying to use NavigationViewItem.Icon property with the CommunityToolkit.WinUI.UI.Controls library. The error is: Microsoft.UI.Xaml.Markup.XamlParseException: 'XAML parsing failed.'
Is this bug a regression in the toolkit? If so, what toolkit version did you last see it work:
Steps to Reproduce
Can this be reproduced in the Sample App? (Either in a sample as-is or with new XAML pasted in the editor.) If so, please provide custom XAML or steps to reproduce. If not, let us know why it can't be reproduced (e.g. more complex setup, environment, dependencies, etc...)
All you need to do:
Create a new solution with the ProjectReunion version 0.5.5
It's so strange. I've created an absolutely identical WinUI 3 project, added Community controls library, and everything is working. I don't know, what's wrong with this one: https://github.com/LeftTwixWand/ReunionAppBug.git
Someone else has reported something that looks the same in this discussion: #3912 (comment) (apparently GitHub doesn't show mentions in the issue history for discussions).
@LeftTwixWand@azchohfi - thanks for the report. It looks like a change in the Reunion 0.5.5 servicing release isn't playing nicely with Reunion 0.5.0 (some metadata in the Microsoft.WinUI.dll projection was stripped out). This issue can happen when an app and a library it consumes are targeting different Reunion versions, due to the differences in metadata. This should be fixed in the next Reunion servicing release, but in the meantime the app and library should target the same version. For the repro app, it's targeting 0.5.5 while the community toolkit is on 0.5.0. I was able to workaround this by changing the app's Reunion version from 0.5.5 to 0.5.0
Ok, thank you Tommy, this is very helpful! In the meantime, we can also push a new version of the toolkit based on 0.5.5. @michael-hawker , are you ok with us doing this asap?
@azchohfi yeah sounds good. Originally we thought we'd be able to play nicely with the update, but seems like I've heard about a couple of potential issues at this point. Just a rev a 7.0.x version of the WinUI packages and we should be good! Thanks Alex!
The application won't start and I can see in the output windows :
Exception thrown: 'System.NotImplementedException' in CommunityToolkit.WinUI.UI.Controls.Core.dll
Exception thrown at 0x7761A6E2 (KernelBase.dll) in NavigationSample.exe: WinRT originate error - 0x80004001 : 'The method or operation is not implemented.'.
Exception thrown at 0x7761A6E2 (KernelBase.dll) in NavigationSample.exe: WinRT originate error - 0x802B000A : 'Cannot deserialize XBF metadata property list as 'Icon' was not found in type 'Microsoft.UI.Xaml.Controls.NavigationViewItem'. [Line: 0 Position: 0]'.
onecore\com\combase\winrt\error\restrictederror.cpp(1016)\combase.dll!76B511A5: (caller: 76A67BB6) ReturnHr(1) tid(1480) 8007007E Le module spécifié est introuvable.
Microsoft.UI.Xaml.dll!09DAA1B4: (caller: 09C22D09) Exception(1) tid(1480) 80004001 Non implémenté
Exception thrown at 0x7761A6E2 in NavigationSample.exe: Microsoft C++ exception: wil::ResultException at memory location 0x00BBD138.
Exception thrown at 0x7761A6E2 in NavigationSample.exe: Microsoft C++ exception: [rethrow] at memory location 0x00000000.
Microsoft.UI.Xaml.dll!09DAA6DE: (caller: 09C07354) ReturnHr(1) tid(1480) 80004001 Non implémenté
Msg:[Microsoft.UI.Xaml.dll!09DAA1B4: (caller: 09C22D09) Exception(1) tid(1480) 80004001 Non implémenté
]
Exception thrown: 'Microsoft.UI.Xaml.Markup.XamlParseException' in WinRT.Runtime.dll
WinRT information: Cannot deserialize XBF metadata property list as 'Icon' was not found in type 'Microsoft.UI.Xaml.Controls.NavigationViewItem'. [Line: 0 Position: 0]
XAML parsing failed.
I don't know if I missing package or have wrong targetFramework...
@giraudremy - you can workaround this for now by changing the PackageReferences in your .csproj and .wapproj from 0.5.5 to 0.5.0 for Microsoft.ProjectReunion and Microsoft.ProjectReunion.WinUI.
@michael-hawker - you should stay on 0.5.0 until the next servicing release. 0.5.0 and 0.5.6 (or whatever the next version ends up being) will play nicely with each other, but 0.5.5 won't with any of them.
Activity
Kyaa-dost commentedon Apr 20, 2021
@LeftTwixWand Thanks for checking but this issue is specifically a WinUI issue. Please try reporting in the WinUI repo.
michael-hawker commentedon Apr 20, 2021
@azchohfi thoughts on what might be going on here?
LeftTwixWand commentedon Apr 20, 2021
@Kyaa-dost, but if I'm removing the toolkit library - it works fine...
azchohfi commentedon Apr 20, 2021
No idea why this is happening. I was able to reproduce this issue.
@RealTommyKlein, any idea what is going on?
LeftTwixWand commentedon Apr 21, 2021
It's so strange. I've created an absolutely identical WinUI 3 project, added Community controls library, and everything is working. I don't know, what's wrong with this one: https://github.com/LeftTwixWand/ReunionAppBug.git
michael-hawker commentedon Apr 21, 2021
@LeftTwixWand can you do a full diff against the two folders to see if there's anything that may be different?
michael-hawker commentedon Apr 21, 2021
Someone else has reported something that looks the same in this discussion: #3912 (comment) (apparently GitHub doesn't show mentions in the issue history for discussions).
RealTommyKlein commentedon Apr 21, 2021
@LeftTwixWand @azchohfi - thanks for the report. It looks like a change in the Reunion
0.5.5servicing release isn't playing nicely with Reunion0.5.0(some metadata in theMicrosoft.WinUI.dllprojection was stripped out). This issue can happen when an app and a library it consumes are targeting different Reunion versions, due to the differences in metadata. This should be fixed in the next Reunion servicing release, but in the meantime the app and library should target the same version. For the repro app, it's targeting0.5.5while the community toolkit is on0.5.0. I was able to workaround this by changing the app's Reunion version from0.5.5to0.5.0azchohfi commentedon Apr 21, 2021
Ok, thank you Tommy, this is very helpful! In the meantime, we can also push a new version of the toolkit based on 0.5.5.
@michael-hawker , are you ok with us doing this asap?
michael-hawker commentedon Apr 21, 2021
@azchohfi yeah sounds good. Originally we thought we'd be able to play nicely with the update, but seems like I've heard about a couple of potential issues at this point. Just a rev a 7.0.x version of the WinUI packages and we should be good! Thanks Alex!
5 remaining items
giraudremy commentedon Apr 21, 2021
Hi,
Yes I Have the same issue.
I have create a new WinUI from visual studio 2019 (Version 16.10.0 Preview 2.0).
I have added this line from csproj to be able to compile WinUI projet
I have added this line in MainWindow.xaml
If I start the projet at this point, the application run well :

Now if I just added reference ton CTW in csproj by adding this lines :
The application won't start and I can see in the output windows :
I don't know if I missing package or have wrong targetFramework...
RealTommyKlein commentedon Apr 21, 2021
@giraudremy - you can workaround this for now by changing the
PackageReferences in your .csproj and .wapproj from0.5.5to0.5.0forMicrosoft.ProjectReunionandMicrosoft.ProjectReunion.WinUI.LeftTwixWand commentedon Apr 21, 2021
@Kyaa-dost @michael-hawker @azchohfi @RealTommyKlein guys, thank you so much for making amazing technologies)
giraudremy commentedon Apr 21, 2021
@RealTommyKlein Yes it's work with 0.5.0, thank. I will stay with this version until the next relase of WinUI
michael-hawker commentedon Apr 21, 2021
@RealTommyKlein should we wait to rebuild the Toolkit on top of that one? Or if we target 0.5.5 will that still work with the new release coming?
FYI @azchohfi
RealTommyKlein commentedon Apr 21, 2021
@michael-hawker - you should stay on 0.5.0 until the next servicing release. 0.5.0 and 0.5.6 (or whatever the next version ends up being) will play nicely with each other, but 0.5.5 won't with any of them.
michael-hawker commentedon Apr 23, 2021
FYI @azchohfi
RealTommyKlein commentedon Apr 26, 2021
@michael-hawker @azchohfi - 0.5.6 is now available which you can upgrade to.
michael-hawker commentedon May 12, 2021
@LeftTwixWand we just shipped the 7.0.2 version of the WinUI packages on top of Reunion 0.5.6: https://www.nuget.org/packages/CommunityToolkit.WinUI.UI.Controls/7.0.2
Let us know if you have any more issues, thanks!
LeftTwixWand commentedon May 12, 2021
Great job! Thank you, guys)
giraudremy commentedon May 15, 2021
No problem with the 7.0.2 version of the WinUI packages and project Reunion 0.5.7