2 ms·

.NET 5 saw renewed development in WPF, including some useful improvements over WPF in .NET 4.x. They've given the impression that WPF is fully "undeprecated" an

.NET 5 saw renewed development in WPF, including some useful improvements over WPF in .NET 4.x. They've given the impression that WPF is fully "undeprecated" and current documentation points to WPF as the best way to utilize WinUI 3.0 controls (modern Windows controls) in .NET today. (WinForms also saw a bunch of reinvestment in .NET 5 and also has a road to migrate to WinUI 3.0 controls if you really want, but I would argue that WinForms was never a "good desktop UI framework".)

pjmlp 5y ago
Go to their github issues and have fun reading through them. Basically Microsoft had to rampup Windows Forms and WPF teams (most likely ramped down to maintenance modus), as otherwise many companies would just ignore .NET Core. The designers, which were redone to be out of process in .NET 5, still have lots of issues. Basically, the future is UWP/WinUI, but just like with VB 6, there are plenty of big shot customers that want their apps to keep running and aren't open to rewrites. And in what concerns WinUI, MAUI is being built on top of WinUI (with incompatible XAML) and then there is Blazor. Plenty of political wars going on currently in Redmond UI teams.