I haven't touched it in years but I remember moving to WPF because it had a better answer for binding UI elements to data. But while WPF does have an answer, everything is so fucking verbose and clunky.
reply>This barely mentions Windows Forms
replyApparently, you do too, since what you said is basically the same as what the article said (.NET wrapper for C#, fastest prototyping to date)
Winforms is a Win32 API wrapper, so on the same level as MFC, not a separate UI framework.
replyIt is a wrapper, but it's not quite on the same level as MFC. MFC really is a thin wrapper, almost 1:1 in most places. WinForms is more like VCL or VB6 in that it uses Win32 where it can but doesn't design around it, so in practice it's more high-level.
replyI went from win32/C++ to Windows Forms and I got a huge increase in productivity and quality.
replyIt wasn’t all roses though, the high dpi support was atrocious.
I always felt the problem with WinForms was the name. For many, many years I assumed it could only do forms (ie for data entry).
reply