Skip to main content
fixed formatting
Source Link
user
  • 2.2k
  • 8
  • 27
  • 37

There are 2 major reasons:

1 - Lack of multiple inheritance. You can inherit from one base class and implement any number of interfaces. That's the only way to "do" multiple inheritance in .NET.
2 - COM interoperability. Anything that will need to be used by "older" technologies will need to have interfaces defined.

  1. Lack of multiple inheritance. You can inherit from one base class and implement any number of interfaces. That's the only way to "do" multiple inheritance in .NET.
  2. COM interoperability. Anything that will need to be used by "older" technologies will need to have interfaces defined.

There are 2 major reasons:

1 - Lack of multiple inheritance. You can inherit from one base class and implement any number of interfaces. That's the only way to "do" multiple inheritance in .NET.
2 - COM interoperability. Anything that will need to be used by "older" technologies will need to have interfaces defined.

There are 2 major reasons:

  1. Lack of multiple inheritance. You can inherit from one base class and implement any number of interfaces. That's the only way to "do" multiple inheritance in .NET.
  2. COM interoperability. Anything that will need to be used by "older" technologies will need to have interfaces defined.
Post Made Community Wiki by James P.
Source Link
Tangurena
  • 13.3k
  • 4
  • 40
  • 68

There are 2 major reasons:

1 - Lack of multiple inheritance. You can inherit from one base class and implement any number of interfaces. That's the only way to "do" multiple inheritance in .NET.
2 - COM interoperability. Anything that will need to be used by "older" technologies will need to have interfaces defined.