documentation for Singleton Static Initializer

tk-codes · web-flow · commit 6345a35d9112 · 2016-12-21T22:29:29.000+01:00
diff --git a/CreationalPatterns/Singleton/README.md b/CreationalPatterns/Singleton/README.md
@@ -4,7 +4,33 @@
 
 ## Static Initialization
 
-If your applicatioin always creates and uses an instance of the `Singleton` or the overhead of creation and runtime aspects of the Singleton are not onerous, you may want to create your Singleton eagerly, like `ChocolateBoiler_StaticInit.cs`.
+:thumbsup: **You may want to create your Singleton eagerly, if**
+* your application always creates and uses an instance of the `Singleton`
+* the overhead of creation and runtime aspects of the Singleton are not onerous
+
+[ChocolateBoiler_StaticInit.cs](CreationalPatterns/Singleton/ChocolateBoiler_StaticInit.cs).
+```cs
+    public sealed class ChocolateBoiler_StaticInit
+    {
+        // singleton instance
+        private static readonly ChocolateBoiler_StaticInit instance = new ChocolateBoiler_StaticInit();
+
+        public static ChocolateBoiler_StaticInit Instance
+        {
+            get
+            {
+                return instance;
+            }
+        }
+    }
+```
 
 The class is marked as **sealed** to prevent derivation, which could add instances. In addition, the variable is marked **readonly**, which means that it can be assigned only during static Initialization or in a class constructor.
 
+Because the **Singleton** instance is referenced by a private static member variable, the instantiation does not occur until the class is first referenced by a call to the **Instance** property. This solution therefore implements a form of the lazy instantiation property, as in the Design Patterns form of Singleton.
+
+:thumbsdown: **Downside**
+* You have less control over the mechanics of the instantiation
+
+Reference: 
+* MSDN - [Implementing Singleton in C#](https://msdn.microsoft.com/en-us/library/ff650316.aspx)
