Windows Forms
No written verdict yet. Here is what commenters said.
9recommend
4warn against
Nov 5, 2025first mention
Oct 27, 2026latest mention
Why people recommend it
“binding data to controls was dead simple, it felt surprisingly modern”
“the only truly usable products still seem to be WPF and WinForms”
.NET developer in Koreaon “What is .NET, and why should you choose it?”
Show 3 more
“Windows Forms is the answer you seek”
Has shipped Windows Forms apps for 25 yearson “Microsoft Hasn't Had a Coherent GUI Strategy Since P…”
“WinForms still exist, still supported, still getting new features.”
“Windows Forms has fully integrated dark mode support.”
Caveats and dissent
“Windows.Forms is becoming less of a problem”
“WinForms supposedly has some support for high DPI, but with many open issues.”
Show 1 more
Often compared with
Who recommends it in their own words
Threads where it came up
- Windows native app development is a mess 4 mentions
- Microsoft Hasn't Had a Coherent GUI Strategy Since Petzold 3 mentions
- Oldest GUI application that still runs on Windows 11 2 mentions
- Windows 11's Start menu was built using React – now switching to native WinUI 2 mentions
- Show HN: C# Game Engine with its own scripting language and IDE 1 mention
- What is .NET, and why should you choose it? 1 mention
Also written as Windows Forms. Data: windows-forms.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 16
WinForms provided some responsive control patterns like "anchors" and "dock" properties [0] and other sorts of relative positioning. Some third party component libraries included even more advanced layout controls. A lot of applications would add in imperative code to make up for more complex scenarios that anchors/dock didn't handle well enough. WinForms was still built on the back of pixel-perfect positioning assum
“binding data to controls was dead simple, it felt surprisingly modern”
“Windows.Forms is becoming less of a problem”
“the only truly usable products still seem to be WPF and WinForms”
“Windows Forms is the answer you seek”
“WinForms still exist, still supported, still getting new features.”
“what surprised me is how different the rendering architecture is for each framework.”
“Windows Forms has fully integrated dark mode support.”
“WinForms supposedly has some support for high DPI, but with many open issues.”
“It does, but many still think it is like using VB 6”
“I don't think it's abandoned”
“the start menu could have been written in C#, WinForms, and have been far less troublesome”
“better use Win32, Forms, WPF, Avalonia, Qt,...”
From what I can tell taking to people in the discord and stuff, people seem to do it all the time and not run into any issues. Still, it would be neat if they got off winforms and switched to something like Avalonia
“stuck with tried and tested solutions like WinForms with proprietary controls”
“Forget Qt and Windows Forms”