So I'm working on StudioBlogger today, and I have to say that as a WebForms guy, I'm really frustrated at the WinForms architecture. It's extremely obvious that this whole WindowsForms thing was not throught out as well as the ASP.NET side was, and the two teams definitely did not talk to each other. I'm trying to cycle through a CheckedListBox to populate another CheckedListBox with the categories from the selected blogs, and there are like 9 different properties for accessing selected items. None of these properties have any examples whatsoever in the MSDN documentation, and information on the web is scarce at best. Even with all these MSDN developers blogging on this site, real-life WinForms scenarios are not being addressed. They're too busy writing YAGA (Yet Another Generics Article) to pay attention to the basic everyday stuff that app devs need to be able to do. What's the deal?
Whidbey's been delayed. Everyone is bellyaching and b!tching about it, and I say... great! Let it be delayed. There is a TON of stuff that needs fixing in 2.0. My friend Brady Gaster said today "There are so many screwed up parts of the Framework, but it's SO money that you just have to deal with it." I'm tired of "just dealing with it". If 4 more months of waiting means that I have a lot less crap to deal with, then WTG Microsoft for making the tough but right decision. Now will someone PLEASE get the WinForms and WebForms teams in the same room to make this stuff more cross-client compatible?