The Singleton pattern implementation out of the gang of four book [Gamma, Helm, Johnson, and Vlissides. Design Patterns: Elements of Reusable Object-Oriented Software. Addison-Wesley, 1995.] is not thread save (at least in C# it isn\u2019t). Besides that it uses a GetInstance() method and makes not use of C# properties. I think a simple Instance property is nicer and follows the general C# style.<\/p>\n
Check out my version of a Singleton implemenation:<\/p>\n
public class Singleton \n\n{ \n\n private readonly static Singleton singleton = new Singleton(); \n\n public static Singleton Instance() \n\n { \n\n return singleton; \n\n } \n\n private Singleton() \n\n { \n\n } \n\n}<\/pre>\nUpsides of this approach are that it is thread save and look quite simple. Downside is you don\u2019t have exact control over when<\/strong> the Instance is created. In the few cases where this is important (Let\u2019s say the creation of the instance is very time consuming and you want to guarantee that it is only created when needed you might want to check out the double-check locking approach more detailed explained here: http:\/\/msdn2.microsoft.com\/en<\/wbr>-us\/library\/ms998558.aspx<\/a>.<\/p>\nThe double-check locking approach is also a solution if you need to do some extra stuff when you create the one instance.<\/p>\n","protected":false},"excerpt":{"rendered":"
The Singleton pattern implementation out of the gang of four book [Gamma, Helm, Johnson, and Vlissides. Design Patterns: Elements of Reusable Object-Oriented Software. Addison-Wesley, 1995.] is not thread save (at least in C# it isn\u2019t). Besides that it uses a GetInstance() method and makes not use of C# properties. I think a simple Instance property … Continue reading Singleton\u2019s implemented the right way<\/span>