Can we please add support for String overloads wherever we see char[] in the framework?
Aaahhh!
One of my pet peeves, actually, is that sprinkled throughout the framework are many places that insist on taking a char[]. The instance method String.Split() is one such example, though I am certain that you will see many others.
Why, oh why didn't we overload these methods to take a String? It's not like I keep a char[] in my pocket, just waiting to use. I've got to dust off a Char.Parse(), or some such ugly construct.
The String is one of the most natural objects in the framework. Microsoft really got something right here, with a unified string type, instead of the mess of BSTR and LPSTR and char* and CString and wchar and TCHAR and LPCTSTR and basic_string and (breath, Jerry, breath!!)...
And, I'm not even mentioning the custom strings that people write for C++. I think I would run out of blog space here.
So, since the String class is one of the most "natural" types in .NET, a string parameter should be the type of choice when passing charactor data. Does anyone really have a good reason to offer a char[] param, and not a corresponding String overload?