Assuming it is a well-written class with a single specific responsibility then the fact that you are using it everywhere means it is a success.
Look at it this way, is there anything wrong with using System.String or List<T> in heaps of places? If you've written your class well then it should be no problems. The only issue you have is that it will be very difficult to make breaking changes to your class as it will effect a lot of other code. "Framework Design Guidelines" by Cwalina & Abrams has a lot of good suggestions for designing framework code that will be used by lots of clients and therefore should be designed to avoid breaking changes. One of the things mentioned is in fact that abstract classes are more flexible than interfaces in this regard because if you add something to an interface then you break everything that uses it, but with an abstract class you can add something along with a default implementation so it isn't a breaking change. It's an interesting book by the guys right at the coalface of building the .NET framework and well worth a read. Regards, Ben -----Original Message----- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Arjang Assadi Sent: Wednesday, 21 April 2010 10:11 AM To: ozDotNet Subject: Re: Persils of overusing a class? Thank you Preet and Micheal, Assuming it is not a god class and has a very specific responsibility and furthermore it is been used throughout the project very often. Is there such a thing as over dependency/over use?Are there any problems with when too many classes depend/rely on few class/objects for specific functionality? Are there any preferred object interaction/dependency topologies? Regards Arjang This email is intended for the named recipient only. The information it contains may be confidential or commercially sensitive. If you are not the intended recipient you must not reproduce or distribute any part of this email, disclose its contents to any other party, or take any action in reliance on it. If you have received this email in error, please contact the sender immediately and delete the message from your computer.
