2 added 258 characters in body; added 1 characters in body
source | link

There are several reasons why you might want to use interfaces instead of class inheritance:

  1. Interfaces are better suited to situations in which your applications require many possibly unrelated object types to provide certain functionality.
  2. Interfaces are more flexible than base classes because you can define a single implementation that can implement multiple interfaces.
  3. Interfaces are better in situations in which you do not need to inherit implementation from a base class.
  4. Interfaces are useful in cases where you cannot use class inheritance. For example, structures cannot inherit from classes, but they can implement interfaces.

http://msdn.microsoft.com/en-us/library/3b5b8ezk(v=vs.80).aspx

Interfaces are like anything else in programming. If you don't need them, don't use them. I've seen them used extensively as a matter of style, but if you don't need the special properties and capabilities that an interface provides, I don't see the benefit of using them "just because."

There are several reasons why you might want to use interfaces instead of class inheritance:

  1. Interfaces are better suited to situations in which your applications require many possibly unrelated object types to provide certain functionality.
  2. Interfaces are more flexible than base classes because you can define a single implementation that can implement multiple interfaces.
  3. Interfaces are better in situations in which you do not need to inherit implementation from a base class.
  4. Interfaces are useful in cases where you cannot use class inheritance. For example, structures cannot inherit from classes, but they can implement interfaces.

http://msdn.microsoft.com/en-us/library/3b5b8ezk(v=vs.80).aspx

There are several reasons why you might want to use interfaces:

  1. Interfaces are suited to situations in which your applications require many possibly unrelated object types to provide certain functionality.
  2. Interfaces are more flexible than base classes because you can define a single implementation that can implement multiple interfaces.
  3. Interfaces are better in situations in which you do not need to inherit implementation from a base class.
  4. Interfaces are useful in cases where you cannot use class inheritance. For example, structures cannot inherit from classes, but they can implement interfaces.

http://msdn.microsoft.com/en-us/library/3b5b8ezk(v=vs.80).aspx

Interfaces are like anything else in programming. If you don't need them, don't use them. I've seen them used extensively as a matter of style, but if you don't need the special properties and capabilities that an interface provides, I don't see the benefit of using them "just because."

1
source | link

There are several reasons why you might want to use interfaces instead of class inheritance:

  1. Interfaces are better suited to situations in which your applications require many possibly unrelated object types to provide certain functionality.
  2. Interfaces are more flexible than base classes because you can define a single implementation that can implement multiple interfaces.
  3. Interfaces are better in situations in which you do not need to inherit implementation from a base class.
  4. Interfaces are useful in cases where you cannot use class inheritance. For example, structures cannot inherit from classes, but they can implement interfaces.

http://msdn.microsoft.com/en-us/library/3b5b8ezk(v=vs.80).aspx