[DarrenZ]

>the dot net world lacks any sort of real UI building capability

Off the shelf, yes. But third party providers like Devexpress and Telerik have stepped into that gap and now produce some very polished component suites that sit on top of Winforms. At a cost, of course, and more geared towards the enterprise market.

I've used component suites like these in new .Net desktop products and without fail they're received well.

[eropple]

Under no circumstances would I use WinForms for something I have to release to the public in 2017. It was a great API upon release. It's an awful call today, when DPI scaling and similar "this was written with something past Windows XP in mind" concerns are at the forefront.

And, unlike something like Electron.NET (which I wouldn't use either, because I'm not scared of TypeScript, but whatever, I get the reasoning), you're bolted to Windows and Windows alone. Maybe you have no MacOS users, but most folks would like to have those users. If only because they tend to spend more money on software.

[yodon]

Windows forms was the coolest thing I’d ever seen back in 2002, and it’s still my go to for a little window with a couple buttons, but the HTML/CSS ecosystem has so blown past it in the past 15 years that even built on a terrible foundation (CSS when I want Xaml) and a terrible language (JS when I want C#), HTML/CSS still ends up looking like the right choice to me for anything really sophisticated UI/UX wise.

[tonyedgecombe]

My main product is largely WinForms and the UI was quick and easy to develop.

The two downsides that stop me using it now are poor high dpi support and lack of decent cross platform support.

[pjmlp]

High DPI support is available on .NET Framework 4.7.

https://docs.microsoft.com/en-us/dotnet/framework/winforms/h...

EDIT: Typo

[ComputerGuru]

That’s 4.7, not 7.

[pjmlp]

Thanks.