Design and Architecture

Urs Enzler wrote:

Furthermore I request interfaces which allows the replacement of "singletons" either for testing (mocks)

Urs Enzler wrote:

I consider singletons as evil!

Urs Enzler wrote:

The main reason I'm not a fan of the singleton pattern is because it is overused.

Urs Enzler wrote:

Because of these reasons I prefer using a manager pattern (Factory pattern)

led mike wrote:

You probably know this but there are many more creational patterns[^]

Urs Enzler wrote:

but with managing functionality

Urs Enzler wrote:

Depending on configuration and other things it will return me a singleton or a new instance.

<br />
 /// <typeparam name="Type">Any type with a public and parameterless constructor.</typeparam><br />
 public sealed class SingletonCreator<Type> where Type : class, new()<br />
 {<br />
<br />
  #region Private declarations<br />
  /// <summary><br />
  /// The instance to retain after creation<br />
  /// </summary><br />
  private static Type instance;<br />
  #endregion<br />
<br />
  #region Properties<br />
  /// <summary><br />
  /// A lazy instance instantiator property.  It will test for the existence of an object and return that reference otherwise it will create a new object.<br />
  /// </summary><br />
  /// <returns>An singleton instance of type "Type".</returns><br />
  public static Type GetInstance()<br />
  {<br />
   lock (typeof(Type))<br />
   {<br />
    if (instance == null)<br />
    {<br />
     instance = new Type();<br />
    }<br />
    return instance;<br />
   }<br />
  }<br />
  #endregion<br />
<br />
 }<br />

<br />
// This will always create an instance it it doesn’t exist or return the <br />
// existin reference if it was previously called.<br />
MyClass myClass = SingletonCreator<MyClass>.GetInstance();<br />