Interfaces vs. abstract classes

Question

In C#, when should you use interfaces and when should you use abstract classes? What can be the deciding factor?

Solution 1

Update: C# 8.0 New Feature: Beginning with C# 8.0, an interface may define a default implementation for members, including properties. Defining a default implementation for a property in an interface is rare because interfaces may not define instance data fields.

The advantages of an abstract class are:

• Ability to specify default implementations of methods
• Added invariant checking to functions
• Have slightly more control in how the "interface" methods are called
• Ability to provide behavior related or unrelated to the interface for "free"

Interfaces are merely data passing contracts and do not have these features. However, they are typically more flexible as a type can only be derived from one class, but can implement any number of interfaces.

Solution 2

Abstract classes and interfaces are semantically different, although their usage can overlap.

An abstract class is generally used as a building basis for similar classes. Implementation that is common for the classes can be in the abstract class.

An interface is generally used to specify an ability for classes, where the classes doesn't have to be very similar.

Solution 3

Another thing to consider is that, since there is no multiple inheritance, if you want a class to be able to implement/inherit from your interface/abstract class, but inherit from another base class, use an interface.

Solution 4

The real question is: whether to use interfaces or base classes. This has been covered before.

In C#, an abstract class (one marked with the keyword "abstract") is simply a class from which you cannot instantiate objects. This serves a different purpose than simply making the distinction between base classes and interfaces.

View more solutions

Comments

[Brann]

@JaredPar : I guess it's to discourage answering duplicate questions (btw, I'm not the one who downvoted you)

[JaredPar]

@Brann, I've unfortunately seen that behavior before. Seems like it would make more sense to use the down vote on the OP. It's their responsibility to search for dupes.

[Matthew]

I'm surprised this answer has so many upvotes and is the accepted answer. It seems to show the answerer's bias ("advantages of abstract class" followed by four bullets of advantages followed by "interfaces are merely" followed by a single "however" in favor of interfaces) toward abstract classes much more than really describe the differences between abstract classes and interfaces. I am not meaning to attack the answerer but certainly this question should be stated in a more objective way to do the best justice to the question.

[Gigi]

@Matt the answer provides all the relevant facts for both abstract classes and interfaces, so why wouldn't it be objective? I think it's a very good answer.

[James Z.]

The answer by @Guffa is a much better answer as it explains correctly when each should be used.

[Behnam]

Let me do not agree with your opinion about this sentence (but inherit from another base class, use an interface.) because of inheritance = reusability. In general, interfaces don't cover reusability. When we are talking about reusability, we must have an implementation whereas in interfaces we don't have an implementation. That is why interfaces are not for multiple inheritances.