.Net 2.0 Complaints
I'm sick of .Net 2.0, the bugs in it, and the architectural mistakes and missteps that I find each and every day in the new framework. I thought I would get something good, but I didn't, and I'm pissed about it. I don't want to be a kvetcher like this, so here's how I'm going to spin it. Instead of just kvetching about .Net 2.0 problems and bugs and things that just plan out suck, I'll do my best to explain each thing as I find it. Where possible (and it isn't always), I'll even show how I resolved the issue at hand. I figure, (a) MS isn't doing anything about the problems I'm reporting to them, (b) if I'm seeing these things I'm sure someone else is seeing them too and therein not getting any help as I'm not. So I'll do my best to provide some solutions for these problems. Call it community involvement if you want, call it being a good sport or a bad sport, but the bottom line is that the framework is broken and there's a lot of people out there trying to make things happen and failing miserably as a result of there being shortcomings in the framework. The miserable failure will continue to happen because MS is more concerned with releasing a new framework than they are fixing the one they just released. So I'm going to try to show everyone how to work around the problems as I find them. I don't want a medal, I wouldn't accept an MVP, and I sure as heck don't care what anyone thinks about my persistent kvetching.
So that's that. I'll create a new category (or a tag or something) to make your life easier, in case there's anyone out there who's interested in keeping track of how I solve these problems as they arise.