After C# 8.0 how interface are different then Abstract class

Question

In C# 8.0 we can define body of a method in interface and use that implementation of method as default in inheriting classes. Now after this feature introduced, what is the difference between abstract class and interface and how does this feature impact the real definition of interface?

Daril · Answer

An interface is not a class and it is defined by interface. It is an entity. An abstract class should atleast have one abstract method. without having one abstract method, there is no point in declaring that class as abstract. a standard structure is provided by the interface and the derived class must follow it. a class can only inherit only one abstract class but it can inherit several interfaces.

Ahsan Raza · Answer

When to choose between these two. This is a good question and I loved following read on that https://www.codementor.io/vipinc/when-to-use-abstract-classes-and-when-interfaces-c-interview-questions-jtzll1sn7 USE AN ABSTRACT CLASS 1). When creating a class library which will be widely distributed or reused—especially to clients, use an abstract class in preference to an interface; because, it simplifies versioning. This is the practice used by the Microsoft team which developed the Base Class Library. (COM was designed around interfaces.) 2). Use an abstract class to define a common base class for a family of types. 3). Use an abstract class to provide default behavior. 4). Subclass only a base class in a hierarchy to which the class logically belongs. USE AN INTERFACE 1). When creating a standalone project which can be changed at will, use an interface in preference to an abstract class; because, it offers more design flexibility. 2). Use interfaces to introduce polymorphic behavior without subclassing and to model multiple inheritance—allowing a specific type to support numerous behaviors. 3). Use an interface to design a polymorphic hierarchy for value types. 4). Use an interface when an immutable contract is really intended. 5). A well-designed interface defines a very specific range of functionality. Split up interfaces that contain unrelated functionality.

Ishoo Anyal · Answer

I agree with your point here. But, now that I can declare methods in interface as well how should I decide which one to use, abstract class or interface. While multiple inheritance is a byproduct of what interface can provide us i.e real time impact analysis

Ahsan Raza · Answer

Indeed they can be. That's why my statement about method declaration had "By Default" in it. My point is beside method, there are so many other attributes of interfaces which differ them from abstract classes.

Ishoo Anyal · Answer

Please review following link https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/proposals/csharp-8.0/default-interface-methods Interface can have private protected and static members

Ahsan Raza · Answer

Interfaces are still different from Abstract classes. Interfaces support multiple inheritance Interfaces can NOT provide implementation of an abstract class Interface methods are by default public, while in abstract class one may have private and protected methods also Moreover, If you want consumption of your class not to be extended further, Interface is your best friend. Interfaces are really useful if your application has DI Patteren, making it easily testable and re-usable. Further read: https://www.manning.com/books/dependency-injection-in-dot-net

After C# 8.0 how interface are different then Abstract class

Answers (6)