Skip to main content

C# Tutorial - Singleton Pattern [Beginner]


The singleton is one of the most used and well know design patterns in programming. The idea of a singleton is to have a class which can only be instantiated once. These are very useful for state objects and global resource objects. I will go over several different ways to create singletons and also how to create a generic singleton class.

There are several different places you find information on singletons and creating them for all different languages. One great resources is the Gang of Four book, Design Patterns: Elements of Reusable Object-Oriented Software.

One of the main concerns when using/creating singletons is multi threaded applications/environments. The issue occurs when two threads decided to get an instance of a never made singleton then they have the chance of creating two instances. All the solutions I will present are thread safe.

The first solution presented is a singleton class that you would template your classes after. It creates the singleton instance at the beginning of the start of the application, which makes the class thread safe. As you can notice below the class has a private constructor so the class can't be created outside the class. A static private variable to hold our single instance of our class is included along with a method that returns the instance.
public class Singleton1
{
  private static Singleton1 instance = new Singleton1();

  private Singleton1(){}

  public static Singleton1 GetInstance()
  {
    return instance;
  }
}
 
Now to create an instance of this class all we need to do is:
Singleton1 single = Singleton1.getInstance();
 
The second solution uses lazy instantiation, which means that the class is not created until it is needed. This is good if your class is only used on rare occasions and has a decent memory footprint. You will notice in the code below we again have the static private variable but this time it is not set to a new instance. And we have the same empty private constructor and the getInstance method. But this time you see a little more code in the method.

The first thing you will see is a lock command with the parameter typeof(Singleton2). This is locking the code in this block for one thread at a time. And the next item is an if statement to see if we have created an instance yet. If the instance is null we will create one. And finally we just return the instance. Now to get an instance we use the same technique as above.
public class Singleton2
{
  private static Singleton2 instance;

  private Singleton2() { }

  public static Singleton2 GetInstance()
  {
    lock (typeof(Singleton2))
    {
      if (instance == null)
      {
        instance = new Singleton2();
      }
      return instance;
    }
  }
}
 
The last singleton implementation I am going to go over is a generic singleton. This implementation is very similar to the last except that it now uses generics syntax to create a singleton of any class. This does not however prevent the class T from being created by itself. So this implementation has the benefit of being used as is but has the downfall of not being able to force strict control over the singleton.
class GenericSingleton<T> where T : class, new()
{
  private static T instance;

  public static T GetInstance()
  {
    lock (typeof(T))
    {
      if (instance == null)
      {
        instance = new T();
      }
      return instance;
    }
  }
}
 
To use this you simply would use a piece of code like below, assuming you have the class AutoFactory defined. AutoFactory's constructor would also not be able to take parameters in this implementation.
AutoFactory autoF = GenericSingleton<AutoFactory>.GetInstance();
 
This should give a decent understanding of the singleton pattern and how to implement it using C#.

Comments

Popular posts from this blog

C# Snippet - Shuffling a Dictionary [Beginner]

Randomizing something can be a daunting task, especially with all the algorithms out there. However, sometimes you just need to shuffle things up, in a simple, yet effective manner. Today we are going to take a quick look at an easy and simple way to randomize a dictionary, which is most likely something that you may be using in a complex application. The tricky thing about ordering dictionaries is that...well they are not ordered to begin with. Typically they are a chaotic collection of key/value pairs. There is no first element or last element, just elements. This is why it is a little tricky to randomize them. Before we get started, we need to build a quick dictionary. For this tutorial, we will be doing an extremely simple string/int dictionary, but rest assured the steps we take can be used for any kind of dictionary you can come up with, no matter what object types you use. Dictionary < String , int > origin = new Dictionary < string , int >();

C# Snippet - The Many Uses Of The Using Keyword [Beginner]

What is the first thing that pops into your mind when you think of the using keyword for C#? Probably those lines that always appear at the top of C# code files - the lines that import types from other namespaces into your code. But while that is the most common use of the using keyword, it is not the only one. Today we are going to take a look at the different uses of the using keyword and what they are useful for. The Using Directive There are two main categories of use for the using keyword - as a "Using Directive" and as a "Using Statement". The lines at the top of a C# file are directives, but that is not the only place they can go. They can also go inside of a namespace block, but they have to be before any other elements declared in the namespace (i.e., you can't add a using statement after a class declaration). Namespace Importing This is by far the most common use of the keyword - it is rare that you see a C# file that does not h

C# WPF Printing Part 2 - Pagination [Intermediate]

About two weeks ago, we had a tutorial here at SOTC on the basics of printing in WPF . It covered the standard stuff, like popping the print dialog, and what you needed to do to print visuals (both created in XAML and on the fly). But really, that's barely scratching the surface - any decent printing system in pretty much any application needs to be able to do a lot more than that. So today, we are going to take one more baby step forward into the world of printing - we are going to take a look at pagination. The main class that we will need to do pagination is the DocumentPaginator . I mentioned this class very briefly in the previous tutorial, but only in the context of the printing methods on PrintDialog , PrintVisual (which we focused on last time) and PrintDocument (which we will be focusing on today). This PrintDocument function takes a DocumentPaginator to print - and this is why we need to create one. Unfortunately, making a DocumentPaginator is not as easy as