DevExpress supported WinUI for a little while but decided to abandon support.
One of the biggest problems with WinUI compared to WPF is that DependencyProroperty is implemented as native code, so for .NET developers, there is a huge performance penalty getting or setting any property on control.
Visual Studio had a built-in migration utility which could get you 80-90% there. However if the original VB6 was spaghetti code written without Option Strict and Option Explicit enabled you had much bigger problems.
The biggest breaking change was the removal of the global Printer Object so any printing code needed a complete rewrite.
Aspartame is arguably the safest artificial sweetener. It's made of two naturally occurring amino acids and it's rapidly destroyed by the acidity of the digestive system.
One of the biggest problems with WinUI compared to WPF is that DependencyProroperty is implemented as native code, so for .NET developers, there is a huge performance penalty getting or setting any property on control.
https://github.com/microsoft/microsoft-ui-xaml/issues/1633#i...