The Weird and The Wonderful

• If somebody moved all the string handling functions to a single class so they don't have to remember the location of all of them, that would make some sense. Not much, but some.
• If somebody was working with a tool that requires a function be exposed by a custom class in order to make use of it. For example, I work with an open source tool called Umbraco, and it makes heavy use of XSLT. In order to use a built-in .Net Framework function from XSLT, I have to create a wrapper function and change some configuration settings to let the XSLT know which DLL to use.
• IsNullOrEmpty was new to .Net Framework 2.0. If they were using a version of .Net before 2.0, they may have created their own implementation, then replaced it with the .Net version.

gordon_matt wrote:

I dont think anyone can be that idiotic.

public static class StringUtils
{
  public static bool IsNullOrEmpty(this string s)
  {
    return string.IsNullOrEmpty(s);
  }
}

string a = "11";
string b = "";
string c = null;
Console.Out.WriteLine("a -> {0}, b -> {1}, c -> {2}", a.IsNullOrEmpty(), b.IsNullOrEmpty(), c.IsNullOrEmpty());

Console.Out.WriteLine("a -> {0}, b -> {1}, c -> {2}", string.IsNullOrEmpty(a), string.IsNullOrEmpty(b), string.IsNullOrEmpty(c));