Lazycoder

24Jun/053

WinForms 2.0: Still the Bastard Child of .NET Development

WinForms 2.0: Still the Bastard Child of .NET Development: “If WinForms development at Microsoft is being forsaken to flesh out Avalon,
I’m gonna be severely pissed if some of these basics are missing when Orcas
comes out.
Bottom Line: The built-in WebForms controls are head and shoulders
above their WinForms brethren.”

(Via Robert Mclaws.)

I haven’t done much Winforms development in .NET. After having done WebForms development in ASP.NET for about 2 years now I can say if what Robert says is true, that is the saddest thing I’ve heard in a while.

Filed under: .NET, General Leave a comment
  • http://www.codemilitia.com/blogs/tobin.titus/ Tobin Titus

    This is definitely true. I see feature after feature that “didn’t make the cut” simply because they have way too many people dedicated on the unforseable future and not enough people dedicated to the immediate future. Dockable Tool Windows, for instance, have been available in the Microsoft IDEs since when? 5.0, 6.0? We see them in our VS.NET IDE, Macro Explorer, etc. But we don’t see them in our applications and why? We have a toolstripcontainer that allows us to dock toolstrips to any edge of a winform, what would be so hard about making a window do the same thing as their toolstripcontainer (formerly raftingcontainer)? Also, look at the TabControl. Try setting the tabs on the left side of the control. You can do it, but your text doesn’t adjust appropriately. It still writes horizontally instead of veritcally. I could keep going but its useless. If I see one more of my bug reports on these issues marked as “closed/resolved/postponed”, I’m going to scream!

  • Scott

    Yeah. I have a feeling that I’m going to run into a lot of the same issues you and Robert are describing the more I work in System.Windows.Forms. I’m already running into some annoyances with Application.Run. Mainly with the fact that I have to pass in a Form rather than just start the thread with Main and handle the showing/hiding of the forms through a controller class. I can do what I want to do, but I first have to show some Form, hide it, then show the one I want to show.

  • http://www.codemilitia.com/blogs/tobin.titus/ Tobin Titus

    I don’t have it open, but I was pretty sure you could pass in an applicationcontext object instead of a form. This essentially is the only want to start a formless winforms application. I wrote a Kiosk application a few years ago and I used a custom application context to keep the application from falling out of memory if someone found a way to crash the form. The application context would launch another form and always monitored to make sure that something was covering the screen at all times. Not pretty but it worked in a pinch.