[Investigation] Are our named Resources Exposed to Applications Properly?

[michael-hawker]

See start of discussion on this thread here: #3556 (comment)

Describe the bug

When a developer uses the Toolkit they should have access to the style/resources we expose in order to use them as a basis for modifications. On the discussion above, it's unclear if that's happening properly or not...

Steps to Reproduce

Steps to reproduce the behavior:

1. Start a new project
2. Include the Controls package
3. Go to MainPage
4. Add <Page.Resources> and try and create a new style based on a DefaultTokenizingTextBoxStyle
5. Try to use a new style on the control
6. Compile... does this work?

Expected behavior

It should work...

Related to #3602

[alvinashcraft]

So, when I try this, IntelliSense tells me that the DefaultTokenizingTextBoxStyle is not found. It compiles fine, but I get a Xaml error at runtime during app startup.

[michael-hawker]

Thanks for taking a look @alvinashcraft so seems like we may be missing something to expose these. I wonder if this works differently in UWP and that's why WinUI forces the add to App.xaml?

@ranjeshj do you know who we'd talk to about how this system works and if this is expected or not?

[yoshiask]

I wonder if this works differently in UWP and that's why WinUI forces the add to App.xaml?

I'm pretty sure this is correct, I vaguely remember someone from the WinUI team mentioning this limitation. Might have been an early community call or something.

Are there any updates on this investigation? Is the WCT going to do the same as WinUI?

[michael-hawker]

I think this is a platform limitation and related to this issue here maybe? microsoft/microsoft-ui-xaml#3502