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
App throws 'XAML parsing failed' 'Cannot find resource with the Name/Key...' when trying to lookup a default value (brush) or custom theme resource value (color or brush) from with a resource dictionary other than app.xaml.
Seems the app is not able to resolve resources referenced in additional (non App.xaml) resource dictionaries. Neither the standard WinUI control styles/resources, nor the theme resources defined in App.xaml can be resolved.
I am also running into issues with resources not working as expected. I created a control in code derived from ContentDialog and was not able to apply any styles to it.
Please, try to add more than one style to your recourse dictionary. In my case I had the same exception with only ONE style in resource dictionary, but when I added another style, everything worked as expected.
FYI: I've already seen similar issue, and it's a shame that MS can't fix this for years. And as usual, after months, silence is the answer.
Describe the bug
App throws 'XAML parsing failed' 'Cannot find resource with the Name/Key...' when trying to lookup a default value (brush) or custom theme resource value (color or brush) from with a resource dictionary other than app.xaml.
Seems the app is not able to resolve resources referenced in additional (non App.xaml) resource dictionaries. Neither the standard WinUI control styles/resources, nor the theme resources defined in App.xaml can be resolved.
Sample code to demonstrate this issue can be found on GitHub: https://github.com/artkat/WinUIResourcesTest
Steps to reproduce the bug
Expected behavior
Should run fine and be able to find the resources.
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.4.0: 1.4.230822000
Windows version
Windows 11 (22H2): Build 22621
Additional context
No response
The text was updated successfully, but these errors were encountered: