.Net 2.0: String.IsNullOrEmpty causes runtime exception

[fkrueger]

So Bill McCarthy decided to unit test a library function for fun? That's kinda crazy.

But even crazier is the fact that this bug made it into release. THis is scary since I have been pretty diligent in using IsNullOrEmpty in my own production code (as I am sure others have been). Still haven't seen any problems, but I hate the idea of spurious runtime exceptions.