winforms

Meanwhile I am doing a greenfield project in WinForms, because it needs to be integrated into an existing eco-system of applications and components built around WinForms.

My understanding has been the following: [1] WinForms is a very ancient framework for writing traditional desktop applications.

To my mind, all of the points you listed as an advantage you can also find with C#/VB.net using WinForms.

What specifically do you find easier in VB6 than VB.net/C# when writing desktop apps, in particular in relation to WinForms?

Alternatively writing web apps using Knockout seems so much nicer than WinForms and INotifyPropertyChanged hell.

I'd be interested in how that'd be better, today, than C#/WinForms (WPF is nice, but not for quick things).

Windows Presentation Foundation and WinForms will not likely be open sourced so I doubt it will be anytime soon.

I've also never found WinForms or even WPF (most of the time) to be sluggish on even reasonably modern hardware.

I was interviewing student devs recently and was flabbergasted how many of the kids doing greenfield personal projects were still using WinForms.

If you used Winforms or WPF or DirectX, etc.

If I have a greenfield, I'll probably do it in tcl/tk or python/wx but I'm stick maintaining old win32 and winforms stuff for people.

Surprisingly, there was even a winforms update recently.

Most arguments about "minefields" concern Microsoft-specific libraries, such as WinForms and ASP.

I am accustomed to seeing "WinForms is dead" Internet discussions, with people chiming in to point out that it still lives on in many shops.

Winforms is fairly windows centric, but iirc there is a Mono compatability for most of the interfaces...