Question

I currently have a class in which I only have static members and constants, however I’d like to replace it with a singleton wrapped in an interface.

But how can I do this, bearing in mind that every singleton implementation I’ve seen has a static Instance method, thus breaking interface rules?

Answer 1

A solution to consider (rather than hand-rolling your own) would be to leverage an IoC container e.g. Unity.

IoC containers commonly support registering an instance against an interface. This provides your singleton behaviour as clients resolving against the interface will receive the single instance.

  //Register instance at some starting point in your application
  container.RegisterInstance<IActiveSessionService>(new ActiveSessionService());

  //This single instance can then be resolved by clients directly, but usually it
  //will be automatically resolved as a dependency when you resolve other types. 
  IActiveSessionService session = container.Resolve<IActiveSessionService>();

You will also get the added advantage that you can vary the implementation of the singleton easily as it is registered against an interface. This can be useful for production, but perhaps more so for testing. True singletons can be quite painful in test environments.