Tommy Klein

Thanks for the report. The root of your `.xaml` needs to be a `FrameworkElement` since the Xaml compiler expects to be able to use the `FrameworkElement.Resources` property to get its...

> I thought that the compilation process bundled everything into a resources.pri file, and that is why it had to start with "Resources/*". Maybe @RealTommyKlein can clarify. We do bundle...

The syntax in the repro is correct (e.g. `ItemsSource="{local:EnumValuesExtension EnumType=local:SizeMode}"`). However the Xaml compiler doesn't create type information for `SizeMode` in its generated `XamlMetadataProvider` when it only appears as a...

At least for the InitializeComponent replacement, something like this should work: ```cs public MainWindow() { // Remove default compiler-generated InitializeComponent implementation, and use our hand-written one instead //this.InitializeComponent(); this.InitializeComponentCustom(); }...

Thanks Mike for digging into this - yes, x:Bind'ing to named elements outside of the scope is an intentional feature. This is meant to be similar to the ElementName feature...

Unfortunately, I don't believe we can investigate this before the official WinUI 3 release in 2021. For your scenario in particular, you could try adding an `x:Name` to your root...

Hey all, we're still heads-down on major feature work/bug fixes for WinUI and Project Reunion, so there likely won't be any movement on this for several months. Thanks!

Unfortunately this isn't an easy fix on the WinUI side - the metadata loading/reflection the Xaml compiler is pretty dated and can't access custom modifiers for types, and the `System.Runtime.CompilerServices.IsExternalInit`...