why I need an Interface

[=?Utf-8?B?VW1lc2huYXRo?=]

My query is why I need an Interface, since my abstract class does the same
functionality

Interface
No implementation of methods - ------- This can achieved by abstract class
No instance creation just inheriting ----- This can achieved by abstract class

I know using interface we can go multiple inheritance
I am looking in such way the in terms of OOPS in C# what is the significance

Also I know there are certain places (WWF, WCF) only interface allows as
contracts, those things are MS design part.
I am looking why I need interface, if Abstract class does every thing

Thanks & Regards
Umeshnath

[Mr. Arnold]

"Umeshnath" <Um*******@discussions.microsoft.comwrote in message
news:7E**********************************@microsof t.com...

My query is why I need an Interface, since my abstract class does the same
functionality

Interface
No implementation of methods - ------- This can achieved by abstract class
No instance creation just inheriting ----- This can achieved by abstract
class

I know using interface we can go multiple inheritance
I am looking in such way the in terms of OOPS in C# what is the
significance

Also I know there are certain places (WWF, WCF) only interface allows as
contracts, those things are MS design part.
I am looking why I need interface, if Abstract class does every thing

It depends upon what you're looking to do with an Interface, which doesn't
make any difference what layer it is being used.

You want to see the power of using Interfaces, then I suggest you look at
the show below and open your eyes to Interfaces.

MODEL-VIEW-PRESENTER

http://www.polymorphicpodcast.com/

click 'Shows'

click 'Design Patterns Bootcamp: Model View * Patterns*

view parts 1-5