3 ms·
WPF does take time to wrap your head around because it's more complicated, and in a lot of cases writing business apps (which most straight windows apps are) th
by pixie_ 14y ago
WPF does take time to wrap your head around because it's more complicated, and in a lot of cases writing business apps (which most straight windows apps are) there is no need for all the 'power' WPF provides. WinForms is easy to develop using just the GUI designer. WPF you often need to mix your development between the form designiner and the XAML code itself. It's a needless headache. Also WinForms GUI designer translated the design into straight C#. The WPF->XAML->C# conversion isn't readily accessible, or editable by the programmer and is the source of a lot of complexity and confusion. Often typos in XAML can bring a whole application crashing down with not much of a clue to the source of the bug. /rant
- dbattaglia 14y agoThe xaml/designer issue is pretty much what stopped me from diving too far into wpf. Usually if I'm doing Wimdows apps these days it's some utility/internal tool for work, and it's just sooo much quicker for me to whip something up in winforms ( with a nice easy click once deploy). But for something customer facing I would definitely spend the time to learn wpf. I believe the Github GUI app is WPF and that has a pretty cool interface that would be tricky to pull off in winforms (on a side note, I felt really cheesy at first using it over the command line but now I'm hooked).