is there any problem whenever we use abstract class instead?

Question

is there any problem whenever we use abstract class instead of interface class ?

Francis · Answer

is there any problem whenever we use abstract class instead of interface class? First of all, interface is not a class, where abstract class is a "partially implemented" class. ASFAIK, you will go with abstract class in the below scenarios: 1. You are going to build a Parent class. 2. You want to give some concrete methods as well declare some abstract methods. ASFAIK, you will go with interface in the below scenarios: 1. You going to declare only "Contracts" Normally, these kind of considerations will be taken during the design phase of an application. Hope this helps!

Raja T · Answer

Hi, Please refer below links http://www.c-sharpcorner.com/uploadfile/prasoonk/abstract-class-vs-interface/ http://www.codeproject.com/Articles/11155/Abstract-Class-versus-Interface http://www.aspdotnet-suresh.com/2010/04/abstract-versus-interface.html

Ravi Patel · Answer

Hi, go through following references http://www.geekinterview.com/question_details/14763 http://stackoverflow.com/questions/5835311/what-is-the-advantage-of-interface-over-abstract-classes

is there any problem whenever we use abstract class instead?

Answers (3)