>Not quite. The sample I gave used the constructor (New() in VB if IRRC). Ordinary methods aren't quite the same. Defining ordinary methods as static means they can be called without instantiating the actual object: So given:

>public class Framework
>{
>      public static string SayHello()
>      {
>        return "Hello";
>      }
>}

>This method could be used like:

>string s = Framework.SayHello();
>// Rather than:
>f = new Framework();
>string s = f.SayHello();
>// In fact this wouldn't be legal....
>

>Lots of native examples of this behaviour in the .NET framework; Guid.NewGuid() is a classic example....

Thanks, I will have to see if I can switch Initialize() to a New() approach. If yes, then I would have something interesting here.