Where we will use Interfaces and abstract classes in project?

Question

0.00/5 (No votes)

See more:

I have a small doubt. where we will use exactly interfaces and abstract classes in project.

Can any one clarify me...please.

Posted 27-Feb-11 18:56pm

Balu199

Add a Solution

4 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

J a a n s · Answer 1 · 2011-02-27T19:01:00

Solution 1

Hope this helps

Abstract Class versus Interface[^]

Posted 27-Feb-11 19:01pm

J a a n s

Not Active · Answer 2 · 2011-02-27T19:02:00

Solution 2

And what research have you done?

An interface is a contract, it contains no code. An Abstract class can have code. In .NET you can't derive from multiple classes however you can implement multiple interfaces.

Abstract Class versus Interface[^]

Posted 27-Feb-11 19:02pm

Not Active

Sergey Alexandrovich Kryukov · Answer 3 · 2011-02-27T19:43:00

Solution 3

I already answered similar question. In addition to other Answers, please see the discussion on how to decide on use of interfaces vs. abstract classes: How to decide to choose Abstract class or an Interface[^].

Also, one fundamental difference is that interfaces allows for multiple inheritance, in contrast to classes (abstract or not). This is called week form of multiple inheritance and has serious design implications.

—SA

Posted 27-Feb-11 19:43pm

Sergey Alexandrovich Kryukov

Updated 28-Feb-11 15:11pm

v3

Comments

rajivpande86 1-Mar-11 18:17pm

Not in a mood to raise a debate, still I just want to say -though we iterate 1000 times that we can't go for multiple inheritance but can implement multiple interfaces in C#;implementing multiple interfaces is in no way, even comparable, to multiple inheritance.Implementing multiple interfaces is just that we are adding more constraints to our class to bind to.Your opinion awaited!!

Sergey Alexandrovich Kryukov 1-Mar-11 23:10pm

This is called weak form of multiple inheritance; if you look at VMT layout you would see it is a special case of inheritance (not just by syntax); "comparable" is something undefined and does not make any interesting subject of discussion; and interfaces have nothing to do with constraints. Franky, I'm not very interested in exchange of any opinions on the topic. (What I've just written was not an "opinion".)
--SA

Ramalinga Koushik · Answer 4 · 2011-02-28T19:15:00

Solution 4

this[^] might give you an idea.

Posted 28-Feb-11 19:15pm

Ramalinga Koushik