Similar plan, in 2019 I went back going to distributed systems/Web, where Microsoft technologies are one among many others that get used on a polyglot agency, the usual "A jack of all trades is a master of none, but often times better than a master of one.".
For doing Windows stuff, I would rather advocate for Win32, Forms/WPF.
In regards to C++ stuff, either C++ Builder if it fits the budget, or Qt.
It is quite tragic that even MFC has a better development story than WinUI/C++.
They decided to rewrite Xamarin.Forms, it uses WinUI on Windows, Catalyst on macOS, and VS4Mac is now officially dead and one has to use VSCode instead, and they are all into this Blazor Hybrid as well, with Web views.
Comments
Similar plan, in 2019 I went back going to distributed systems/Web, where Microsoft technologies are one among many others that get used on a polyglot agency, the usual "A jack of all trades is a master of none, but often times better than a master of one.".
For doing Windows stuff, I would rather advocate for Win32, Forms/WPF.
In regards to C++ stuff, either C++ Builder if it fits the budget, or Qt.
It is quite tragic that even MFC has a better development story than WinUI/C++.
How about .NET MAUI?
They decided to rewrite Xamarin.Forms, it uses WinUI on Windows, Catalyst on macOS, and VS4Mac is now officially dead and one has to use VSCode instead, and they are all into this Blazor Hybrid as well, with Web views.
Take your own conclusions on its future.