How can I decide that I should use Static class or singleton class ??

Question

5.00/5 (1 vote)

See more:

C#

.NET

Hi,

How can I decide that I should use Static class or singleton class ??

Thanks,

Posted 6-Dec-10 4:57am

mohammad Taraby

Add a Solution

5 solutions

Solution 5

Static is a concept from the language point of view. Static means you dont create an object.

But Singleton is a concept which lets you create only one instance variable.

It depends on your requirement. If you can tell me what is your requirement, it would be better to give you answer.

Posted 7-Dec-10 21:08pm

Abhishek Sur

Solution 1

Try google.[^]

Posted 6-Dec-10 5:01am

Kschuler

Solution 2

When you want certain methods to be accessible without creating an instance then create it as static. Static class is used for shared variable usage mostly. Even you can create static methods and vars in non-static class also.

For more details and example you should use Google. You can search for details that match your particular requirements.

Posted 6-Dec-10 5:13am

sandipapatel

Updated 6-Dec-10 7:45am

v2

Comments

Pete O'Hanlon 6-Dec-10 13:46pm

This doesn't really answer the OPs question, now does it? You've added exactly zero to his ability to make an informed decision here.

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Simon P Stevens · Accepted Answer · 2010-12-06T05:27:00

The singleton pattern is a object creation control pattern. It allows you to control the instantiation of your object (in this case by restricting it to just one instance).

On the other hand, static classes are not instantiable at all.

Try and think about what abstraction model you are trying to build. If your class represents something tangible, (only one of which should ever exist) you should probably use a singleton. If you are just writing some helper methods you should probably make them static.

It's also wroth considering that the singleton pattern allows for future alteration of the creation control algorithm to allow a managed number of multiple instances.

All this considered, it's also worth noting that in many cases singleton classes don't actually bring a huge amount of benefit but add complexity and can cause tight coupling of your classes. They essentially form a global variable accessible from everywhere. Unless your class really does represent some restricted global system resource, perhaps it's worth considering some kind 'create and pass down' or an IOC/dependency injection pattern to manage your class creation instead.

mohammad Taraby · Accepted Answer · 2010-12-07T20:53:00

1. Singleton gives a reference/pointer to the class instance. You can then pass this reference as a parameter for some other function.

2. You can't extend static classes, but singletons you can, Since static classes are implicitly sealed.

3. with Singleton you can control the amount of users that can use it at the same time.