Re: Instance vs Static + Option

There isnt enough context to go off, but I would personally prefer an =
instance over statics.  I have found that as soon as I even hint at the =
word =22helper=22 it polarizes my subsequent thoughts on how to design =
something.  Rarely in my experience do I see a helper without statics (a =
recent project was more helper than anything else), so as soon as I use =
the term, I immediately think it will probably have statics. =20

Nick.

> -----Original Message-----
> From: brady=40chasesoftware.co.za
> Sent: Wed, 7 May 2008 14:39:36 +0200
> To: dotnet-clr=40discuss.develop.com
> Subject: =5BDOTNET-CLR=5D Instance vs Static + Option
>=20
> I am busy with a new ConfigHelper class, and can't seem to decide on
> which
> approach to take.  The class is responsible for adjusting the config
> table
> in two databases, control and test.  My dilemma is whether I make
> ConfigHelper a static class, and tell it which database to access for
> each
> task, or use instance methods and have one instance for each database.
>=20
>=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> This list is hosted by DevelopMentor.  http://www.develop.com
>=20
> View archives and manage your subscription(s) at
> http://discuss.develop.com

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
This list is hosted by DevelopMentor=AE  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com