Resource Dictionnary requires adding material resources by hand in order to recognize them

[Lee31416]

Hi,

Is it normal that I need these lines

for my resource dictionnary to find the material resources ? These lines were required in a style file (TextBox.xaml) and my resource dictionnary was added after material resources in the App.xaml

[kazo0]

Hi @Lee31416,

Those lines should only be required within the MergedDictionaries of your App.xaml. So are you saying you have that in the App.xaml but your custom TextBlock styles still aren't working unless you initialize Material within your TextBlock.xaml file?

Would you be able to provide the contents of your App.xaml so maybe I can spot where the issue is?

[jeanplevesque]

@kazo0 What's up with this?

[jeanplevesque]

@kazo0 Any update?

[kazo0]

@jeanplevesque sorry, investigating again now, will let you know

[kazo0]

Okay, so after more investigation, it seems that this is an issue on Windows when you are trying to add a ResourceDictionary containing a SINGLE style within the ResourceDictionary. So, if you were to just add some bogus dummy second Style to that TextBox.xaml, everything should work fine.

@jeromelaban
Repro app here (notice the crash when trying to run the Windows head, simply uncomment the MySecondButtonStyle definition in Button.xaml and the app will no longer crash

UnoApp21.zip

I'm assuming maybe Windows is trying to do some fancy inlining optimization if you are trying to include a ResourceDictionary that only contains one resource definition??

[jeanplevesque]

@Lee31416 Can you try this workaround to see if it resolves the issue?
Basically you need your dictionaries to contain at least 2 resources.
That should allow you keep files like TextBox.xaml clean.

@jeromelaban @kazo0 I'm guessing this is a windows bug that we could report. Where would be the best place to do that?

[kazo0]

Yeah I'm still fiddling with it to see what would be a good repro sans uno.material but I think it must be a bug with Windows, right?

[jeromelaban]

@kazo0 yeah it may be. We may isolate this in a winappsdk only sample and create an issue on the WinUI 3 repo then.

[Lee31416]

Yes I can confirm that it works having 2 styles fixes the problem