4 ms·
I left Windows programming around 2006 or so, when it was Win32 and maybe MVC if C++ was your thing. Recently was noodling around with the idea of porting one o
by ryandrake 5y ago
I left Windows programming around 2006 or so, when it was Win32 and maybe MVC if C++ was your thing. Recently was noodling around with the idea of porting one of my hobby projects to Windows, and a just can't believe the mess the platform has become! Now we have Windows Forms, dotNet, WPF, UWP, WinUI, and probably a dozen more. What API should I use to "get back into Windows"? Will it be deprecated next year? If I pick the wrong one, and drive the train down those tracks for a few months, am I basically throwing all the code away? What an absolute mess!
- thrower123 5y agoWinForms is the one to pick if you want something that will work forever and always be supported.
- tonyedgecombe 5y agoIt's not great though unless your requirements are rudimentary. I wasted a huge amount of time on supporting high-dpi. The architecture is archaic.
- ripley12 5y agoBased on everything I've seen in the last year and a half: WebView2 (i.e. Chromium) is getting more investment from the Windows team than any of the "native" UI technologies. I'm not thrilled about it but I'm adjusting my plans accordingly.