-----------------------------------------------------------
New Message on BDOTNET
-----------------------------------------------------------
From: naveeny[MSFT]
Message 4 in Discussion
Hi, In addition to what has already been mentioned above about interfaces there are
couple things from a design perspective: 1. Inheritance model by definition implies
that you have a understanding of the implementation and/or design of the class your
are inheriting from and in many cases this not only creates heirarchies that are
complex but also creates unwanted complexities in systems that are not designed
carefully. 2. Interfaces can be used to be expose different views of an class to
different instantiators of the class or in different control flows within the same
class: class Foo: IInterface1, IInterface2 { } class Foo1 { // Condition check
IInterface1 obj1 = new Foo();
} class Foo2 { // Condition check IInterface2 obj1 = new Foo();
} For all the above reasons the world of design and in particular design patterns
relies heavily on interfaces which provide cleaner more decoupled approach to
designing systems and frameworks that can be extended. I do not want to discount the
use of abstract classes as a useful tool in designing system - but use it with careful
consideration. Thanks, Naveen
-----------------------------------------------------------
To stop getting this e-mail, or change how often it arrives, go to your E-mail
Settings.
http://groups.msn.com/BDotNet/_emailsettings.msnw
Need help? If you've forgotten your password, please go to Passport Member Services.
http://groups.msn.com/_passportredir.msnw?ppmprop=help
For other questions or feedback, go to our Contact Us page.
http://groups.msn.com/contact
If you do not want to receive future e-mail from this MSN group, or if you received
this message by mistake, please click the "Remove" link below. On the pre-addressed
e-mail message that opens, simply click "Send". Your e-mail address will be deleted
from this group's mailing list.
mailto:[EMAIL PROTECTED]
