3 ms·
WebForms can die in a fire, and thankfully has, for the most part, but WinForms is still plenty good enough for cranking out quick and dirty tools. Maybe I'm o
by douche 10y ago
WebForms can die in a fire, and thankfully has, for the most part, but WinForms is still plenty good enough for cranking out quick and dirty tools. Maybe I'm old, or it's just because I started out in high school doing VB6 forms applications, but I still prefer it unless I have a good reason, over WPF.
WinForms is also a pretty thin layer over Win32 controls, as well, so if you have to switch between .Net and native C/C++ Windows dev, it's less of a context switch.
- themartorana 10y agoWebForms changed the game. ASP was a sub-subset of VB, but WebForms with C# made websites full-scale eventful and stateful programs for the first time. I had never felt such power and freedom programming for the web. Yes, some people would put humongous data structures in view state, and yes, more-better solutions have arisen, but WebForms deserves your respect!
- robin_reala 10y agoIt really doesn’t. I’ve never seen a good WebForms site / app and I’ve always dreaded working with them. They were a regressive step.
- insulanian 10y agoIf you worked long enough with WebForms, then you'd know what an inefficient, slow and complicated event-hairball it is. I curse every time I have to go back to any old WebForms-based project to do some changes.
- flukus 10y ago> WebForms with C# made websites full-scale eventful and stateful programs for the first time. And that is why it can go die in a fire!