Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • 8
    +1 for the key point that more than one interface can be implemented on a class. Commented Apr 17, 2009 at 16:50
  • That's the one real advantage to interfaces over abstract base classes, IMO. Otherwise, I agree with the .NET design guidelines, that now say to "prefer abstract base classes over interfaces" Commented Apr 17, 2009 at 16:51
  • Although, it would be keen if you could add the point that it's also interfaces can be applied to any class. Commented Apr 17, 2009 at 16:52
  • 1
    @altCognito: Figured that was kind of handled with the second paragraph. This did remind me, though, that interfaces work on value types, so I added that. Commented Apr 17, 2009 at 16:59
  • Thank you very much for this exact description. It is indeed very helpful. I am new here. It is a pity you cant select two responses as "answer". One thing that confuses me is your usage of Abstract 'base' class. All abstract classes are meant to be a base class of a subclass. Why naming the 'base' extra? Commented Apr 17, 2009 at 17:20