Nick Sabalausky Wrote: > I've thought about that and I don't know how I feel about it. On one hand, I > can certainly image cases where the distiction between null and empty would > be useful. But OTOH, after having to put up with the nightmare of VB6's "One > million distinct ways to have a string that doesn't contain anything", I'm > hesitent at embracing extra ways to have "ain't nuthin' here". >
In our project we use if(string.IsNullOrEmpty(str)){...} almost everywhere only in two places null matters. T__T