Recommendation and suggestions for C# Helper Classes

Question

3.50/5 (4 votes)

See more:

Hi Everyone,

I found that SqlHelper class made development easy as well as cost effective. I am trying to build new project which will contain most of Helpers classes to make a developer's life easy. I want your recommendation and suggestions for this project, which you may use or want to use.

It might not be consider as question, but important.

Regards,
Aman

Posted 15-Apr-12 21:36pm

Aman4.net

Add a Solution

Comments

V. 16-Apr-12 5:16am

SqlHelper is that something you wrote yourself? I'm guessing you want to create a 'framework' assembly with often used functionality, right?

Aman4.net 16-Apr-12 5:32am

Yes, I want to create a group of assemblies which help to perform often used functionalities. I am talking about SqlHelper which is a part of Microsoft.Application.Block.

V. 16-Apr-12 7:39am

Did you use the reply button? I happened to check back on this, but I never received a notification.

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)

V. · Accepted Answer · 2012-04-16T01:38:00

You're talking about a "Framework", "Tools", "Utilities", ...
I've made a few myself, although I don't claim to be an expert, here are my recommendations:

- If possible avoid references of other assemblies that need local copy, if you just have one, you could possibly live with it, but if you start referencing assemblies all over the place it will cause a nightmare (dll hell etc...)

- Try to group functionality together eg. Database access, XML handling, Configuration, Logging, etc...

- What's in a name? Everything! Make sure you have a nice namespacing convention. Note that sooner or later you might need to include a third-party product that also has an assembly with name "XYZ". I often use something like CompanyName.Framework.Functionalitygroup

- Note that you can create a framework solution with multiple projects, effectively creating multiple assemblies which you could reference seperately if you want.

- Add the assemblies to the GAC (implies strong naming), else you just end up copying files all over the place and especially if you're working in a team, you'll end up in tears.

- If you're using the Enterprise assemblies from Microsoft, stay 100% Microsoft, if not (you need to use Oracle for example) don't use it.

- These assemblies are probably used very often, test them over and over and over again and make sure you do performance and load tests.

Hope this helps.

(PS: countered the 1 vote)