3 ms·
From what I have seen I don't know if WPF is at the adoption that Microsoft had hoped for. There is still a lot of development done in WinForms and a lot of th
by jwarzech 15y ago
From what I have seen I don't know if WPF is at the adoption that Microsoft had hoped for. There is still a lot of development done in WinForms and a lot of that work has been migrated to ASP.net for years.
Some of the reasons I've seen quite a few devs not adopt WPF:
- XAML a.k.a. super wordy xml? Why not just drag-and-drop-click-events
- MVVM Template, Caliburn, Prism, or just do things how we did in WinForms?
- Expression Blend makes sense in Microsoft's vision but how many small shops have dedicated UI designers?
- We are moving everything to the web already why would we do another desktop app?
Of course I say that as someone who actually quite enjoyed doing WPF development for three years.