Multiple occurances of static methods and classes

Question

0.00/5 (No votes)

See more:

I've read some conflicting information about the static modifier. First off, a video recorded by a .NET trainer recently said that the static modifier isn't used that often, which I found strange because I'm using it quite a bit. I've been working with C# code for years, but never at the level I am now, so I'm wondering if maybe I'm using it wrong.

Can the methods and class used to connect to SQL Server be static, even though I may be connecting to two different databases, over two different connections? No, right? That would be two instances of the class, right?

Static classes require fewer keystrokes and so I love them. However, piling on two many extension methods in a class library can make the context menu confusing.

Any input would be great.

What I have tried:

My database connection methods are instance methods, which requires the use of MyObj dbobj = new MyOb();

Posted 22-Dec-17 9:19am

User98743

Updated 22-Dec-17 9:47am

Add a Solution

1 solution

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)

OriginalGriff · Accepted Answer · 2017-12-22T09:47:00

In the case of DB connections (and Commands, Adaptors and such like) these should be instances: because they should be Disposed as soon as possible to ensure they don't "linger" and mess things up later (they are scarce resources, so they should be released properly.
The easiest way to do that is via using blocks:

C#

using (MyObj dbObj = new MyObj())
   {
   ... use it here ...
   } ... destroyed when it goes out of context.

Static isn't used that much - I use it when I need data that is common to all instances, and for methods that don't need instance data.

I suspect the video trainer was overgeneralising: but I only use extension methods when I'm expanding existing sealed classes - string for example - for classes "I control" I'd use instance methods. The "less typing" bit is generally untrue, as most of the time a static method needs the class name for the call as well as teh method name - just like an non-static method needs the instance variable name.