When to consider a singleton
Channel:
Subscribers:
5,410
Published on ● Video Link: https://www.youtube.com/watch?v=Ozx4Fvu3jwo
You basically want a singleton when you are sure it is never appropriate to create more than one instance of the class per assembly, yet you require an instance for one reason or another (derivation, easy serialization, properly representing a model). And singletons can ease implementation as only the type needs to be defined and no instances need to be created manually.
Other Videos By Brian
2016-10-04 | Brian's Live Stream |
2014-09-21 | C# - Class Library Overview |
2014-09-14 | The Keys Enumeration |
2014-09-14 | C# - Implicit vs. explicit interface implementation |
2014-09-14 | C# - where constraints |
2014-09-14 | When to consider a singleton |
2014-09-13 | I am programming things |
2014-09-12 | C# - Memberwise cloning with ICloneable |
2014-09-10 | C# Static Constructors |
2014-08-19 | Bindable HasText for WinForms TextBox |
2014-08-19 | Compile C# with CodeDom |
2014-08-11 | C# Rubik's Cube Simulator |
2014-07-13 | New Programming Den! V2 |
2014-07-09 | .NET NinjaWords API |
2014-04-03 | Morse Code Rain |
2014-02-14 | The dramatic reading of YouTube comment |
2014-01-31 | NAudio - C# Show Device master peak in realtime |
2014-01-31 | NAudio fun |
2014-01-22 | Image Viewer Enhanced Enhancements |
2014-01-15 | .NET Regex - Backreferences |
2014-01-14 | C# Xml Serialization |
Tags:
csharp
c#
visual studio
programming
tutorial
learn
c sharp
how to
.net
singleton