Singleton Design Pattern in C# - Do it THAT way
Vložit
- čas přidán 23. 11. 2022
- 🚀 C# Progress Academy - Become a job-ready C# and Angular web developer to land your dream developer role: bit.ly/45vbPUg
🏃♂️ Learn HOW TO work with SINGLETONS in C# with these easy steps!
We'll make sure to make a Developer out of you in no time!
So, what is C#?
C# (pronounced "See Sharp") is a modern, object-oriented, and type-safe programming language. C# enables developers to build many types of secure and robust applications that run in .NET. C# has its roots in the C family of languages and will be immediately familiar to C, C++, Java, and JavaScript programmers. This tour provides an overview of the major components of the language in C# 8 and earlier. If you want to explore the language through interactive examples, try the introduction to C# tutorials.
And what about Singletons?
In software engineering, the singleton pattern is a software design pattern that restricts the instantiation of a class to a singular instance. One of the well-known "Gang of Four" design patterns, which describe how to solve recurring problems in object-oriented software, the pattern is useful when exactly one object is needed to coordinate actions across a system.
More specifically, the singleton pattern allows objects to:
Ensure they only have one instance
Provide easy access to that instance
Control their instantiation (for example, hiding the constructors of a class)
To learn more, make sure to watch the video, and we promise you that you'll become a C# developer in no time! Have fun!
#csharp #dotnet #coding #tutorial #learn #microsoft #net #singleton #pattern #designpatterns
TAGS
dotnet,csharp,dotnet core,.net core tutorial,.net core,.net,c#,Tutorials,Tutorial,Programming,Course,Learn,Step by step,guide,programmer,core,code,c sharp,sharp,net6,6.0,.net framework,programming,visual studio,programming for beginners,coding,how to code,dot net,c# programming,tim corey,software development,singleton,gang of four,singleton design pattern,design pattern,design patterns,data structures,java,dynamic programming,singleton in c#,pattern
tutorialsEU offers you free video tutorials about programming and development for complete beginners up to experienced programmers.
This includes C#, Unity, Python, Android, Kotlin, Machine Learning, etc.
Stay tuned and subscribe to tutorialsEU: goo.gl/rBFh3x
Android: / @tutorialseuandroid
C#: / @tutorialseuc
Unity: / @tutorialseuunity
Facebook: / tutorialseu-1093802040...
LinkedIn: / tutorialseu
Discord: / discord
🚀 C# Progress Academy - Become a job-ready C# and Angular web developer to land your dream developer role: bit.ly/45vbPUg
This is the best Singleton tutorial i've come across. Great stuff!
Nice tut, but I must say that it does not explain when and why I should use such pattern, I think it would nice to have something like that but more orientated to a real scenarios because this is too simple
Simple and precise
Helped a lot, thanks
Excellent demonstration
easy to follow. Best Tutorial ❤
Glad you think so!
Thank you!
Nice! Great job 👏🏻👏🏻👏🏻
Thanks! 😊
explained very easy way 😊
sehr schön erklärt @ 08:42 .. lock gab es auch schon in delphi 5, eine sehr nützliche Funktion um gleichzeitige threads doch noch unter Kontrolle zu bringen *g
This is great tutorial. Can you please add more videos for other design patterns like strategy, observer, facade etc?
Thanks !
Pls do videos on other design patterns as well
Superb
I have one dought. What is the use of sealed keyword when the constructer is already private?
good one
What if we have a distributed environment , multiple instance of this service would be running, how do we prevent multiple instances then?
Nice tutorial
Thank you! Cheers!
Wouldn't it make more sense to remove the outer check for the null instance? I say that because you now have the same condition duplicated in your code which isn't ideal or efficient.
If the outer check is removed, the application will acquire a lock every time the instance is requested, impacting performance.
How about this approach?
namespace SingletonConsole
{
public sealed class UploadService
{
private static UploadService _uploadService;
private UploadService() { }
static UploadService()
{
_uploadService = new UploadService();
}
public static UploadService Instance()
{
return _uploadService;
}
}
}
Static constructors in C# are thread safe, so this will guarantee that _uploadService is initiated only the first time UploadService is referenced.
@8:40 is the critical section of this video thread.
❤
Hi there very interesting tutorial.
Unfortunately though I'm receiving two errors:
1. Program does not contain a static 'Main' method suitable for an entry point (CS5001)
2. When I try to pass values from my instance threads it says that UploadService is inaccessible due to the protect level of my class being sealed/private.
I'm new to programming so I'm a bit lost at the moment as I had to create a new project/program to link it with the UploadService class. What should I do?
Hi, awesome that you try it out!
Make sure that your program cotains a "static void Main" and that you create a "public class UploadService". Also set your program class itself to "public".
Greets :)
Instead of manually managing a lifetime for a service, using static etc it should be done via DI container and in the real world nobody does it the way in the video.