Extending ContentDialog with generics <T> stops autogenerated code

[karmeye]

Describe the bug

ContentDialog can be extended as shown in the example here. This works fine but as soon as I add a generic type InitializeComponent and other autogenerated code is not generated anymore.

Steps to reproduce the bug

See the screenshots.

Expected behavior

Is this not supposed to work?

Screenshots

Adding generics

NuGet package version

WinUI 3 - Windows App SDK 1.5.3: 1.5.240428000

Windows version

Windows 11 (22H2): Build 22621

Additional context

I assume this is the case for all controls, not just ContentDialog.

Thanks

[JohnnyWestlake]

InitializeComponent requires you having a matching XAML file with a matching x:Class="MyClass" set on the root element. However the XAML schema used in UWP/WinUI 3 doesn't support generic class declarations so you can't actually do it.

(The WPF schema supports it :') )

You would need to have an intermediate declaration that solidifies an implementation like
public abstract class BoolContentDialog : ContentDialog<bool> { ... } and use that as the base of your class that wants a XAML file.