Sometimes I'm just plain shocked by the size of the .NET Framework. Usually, this is a good thing... as when I'm impressed with just how cool something is (say.... TypeConverters -- what a killer concept).
Sadly, there are times when I also realize how vast the framework is because of the lack of documentation. As in this example from MSDN. Not ONE example of how that would be called I mean, yeah, I'm a big-boy so I CAN figure it out. But nothing paints the way to quick cognitive implementation like an example. Oh well....
Comments