❔ ✅ WPF Class derivation where both classes have XAML pages
Is it OK for base WPF class to have a XAML page and its derived class to also declare one? So we'd have
X deriving from Y with the following files existing: x.xaml.cs, x.xaml, y.xaml.cs, and y.xaml.4 Replies
there's nothing WRONG with that, per-se, but I question what the use-case is
Well, it didn't work. I ran into an error specifically for this situation. https://learn.microsoft.com/en-us/troubleshoot/developer/dotnet/framework/general/error-mc6017-define-class-xaml
Build error MC6017 when you define a class - .NET Framework
This article provides resolutions to solve the build error MC6017 when you try to define a class that derives from a XAML-generated class.
It would've been so helpful.
Was this issue resolved? If so, run
/close - otherwise I will mark this as stale and this post will be archived until there is new activity.