4 ms·

That sounds great on paper but XAML Islands introduces insurmountable airspace issues. For example, you can't have a nice acrylic window--per Fluent design--and

• WorldMaker 7y ago
  > That sounds great on paper but XAML Islands introduces insurmountable airspace issues. For example, you can't have a nice acrylic window--per Fluent design--and draw your existing WPF XAML on top. It's a non-starter in most cases. If you are already using XAML, the WPF => UWP XAML transition shouldn't be so much of a hurdle as to be a "non-starter in most cases". In most Enterprise CRUD the biggest problem is DataGrid, but you pull one in from the Community Toolkit or one of the 3rd Party components vendors like Telerik. WinUI is talking about first party formally "Fluent" productizing the Community Toolkit's version sometime later in the 3.x timeline. Of course, my view of it is biased by doing a bunch of WPF <=> Silverlight XAML transition work by hand for a few years, and compared to that era, WPF <=> UWP is a lot more civilized. > WinUI 3 has yet to be released. (It's only barely in alpha now.) I forgot that part. Just replace WinUI 3 with WinUI 2 for "today" (up until 20H1, supposedly), and my statement stands.