using static method in c# is good?

[Fabianob]

Nowadays we see the use of methods statics a lot in C#, but if we look for OO that generates a good controversy, because the method statcs aligns the calls and depending on I number him/it of calls can take Time Out then somebody has some concept different from mine regarding the use of methods or classes staticas. An example: If we have the object chair while I am seating nobody more he/she sits down if he goes an object statico, but if we create a new more stancia we will have a new chair so one more person can sit down!

[Shashi Sadasivan]

Static methods and classes generally relate to the singleton pattern.
Its not about c# its about OOP's

so if it is goot for C++ its the same for C#, its how you implement it.

For your wheelchair, you could have instance so taht you can have one wheelchair for eevry user, however servicing might be done only by the manuacturer, or a certain type of wheelchair object has a single manufacturer, would you like to keep assigning the value of the manufacturer eevrytime you instantiate it? (which can lead to al lot of trouble) or would you like to keep it static, so that you can always find who the manufacturer is without having to assign it each time you create the instance?

I have used singletons for contacting paid 3rd party sites where i take information about certain conditions and my other processes use this information.
now every such transaction costs money?
IF that was finding temperature, would you like calling the service each time the process requires it, or would you like to call it once and store it somewhere!

i hope I made sense, otherwise search online for singleto patterns

[r035198x]

Use static variables/methods for fields/actions that are shared among all objects of the same class. If an object is allowed to have it's own value for a certain field or it's own implemenation for a certain action then that field/method should not be declared as static.
Most people misuse the modifier just to make their code compile and run.

[code4life]

Check out this link:
http://en.wikipedia.org/wiki/Singleton_pattern#C.23

There's a subtle difference between static methods and the singleton pattern. For example, you can pass a singleton as a parameter between interfaces/methods/etc., but how would you do that with a static method? As you keep working with the singleton pattern it will become obvious that there is a philosophical difference btw the static methods & the singleton pattern.

That's not to say that using static methods is bad or that singleton pattern is bad. Just that we need to take note of the (subtle) difference between the two.

[Plater]

I use statics to perform usefull program wide functions.
Such as making a log entry.

public static void WriteErrorLog(string Message)
{...}
public static void WriteUsageLow(string Message)
{...}
 

[r035198x]

I use statics to perform usefull program wide functions.
Such as making a log entry.

public static void WriteErrorLog(string Message)
{...}
public static void WriteUsageLow(string Message)
{...}
 

I hope all those those methods are in some Logger class rather than in a Person or Customer class.


The only link between statics and the singleton is that there is only one memory location reserved for a static field that is shared among all objects of the same class. With the singleton "pattern" only one instance of a class is allowed at a time during the lifetime of the program.

Aside from that the two are quite different.
Statics are allocated/resolved at compile time (even though they cannot be called on type parameter types). A singleton is not created at compile time but is an object created dynamically on the heap. The rule is that once one is placed there no other object of the same class can be created.

[Plater]

I hope all those those methods are in some Logger class rather than in a Person or Customer class.

Yes, I just realized after I started typing the example that it would be to big to include all that stuff. I have a static Logging class so it's Logging.WriteErrorLog()