Interface vs. Abstract class

[Valmont]

Moving from C++ to C# .Net:

Why does an interface exist in C# when I can create one by making all methods in
the abstract class "pure virtual"?
Did I miss something conceptually or is the "interface" just here for my
conveniance?
If it is a convinient thing, what style is accepted by the C# community (or mcsd
requirements) as the standard?

[Barry Kelly]

"Valmont" <ax***********@hotmail.comwrote:

Moving from C++ to C# .Net:

Why does an interface exist in C# when I can create one by making
all methods in the abstract class "pure virtual"?

Because .NET doesn't support multiple inheritance.

Did I miss something conceptually or is the "interface" just here for my
conveniance?
If it is a convinient thing, what style is accepted by the C# community (or mcsd
requirements) as the standard?

Interfaces are also useful in their own right, since the notion of a
stateless "supports" relationship is distinct from a class-based "is-a"
relationship.

Interfaces also have downsides that make abstract base classes
preferable in many situations - I made a post in this group a few days
ago in response to Jon Skeet listing some of them.

-- Barry

--
http://barrkel.blogspot.com/

[Valmont]

"Barry Kelly" <ba***********@gmail.comschreef in bericht
news:65********************************@4ax.com...
| "Valmont" <ax***********@hotmail.comwrote:
|
| Moving from C++ to C# .Net:
| >
| Why does an interface exist in C# when I can create one by making
| all methods in the abstract class "pure virtual"?
|
| Because .NET doesn't support multiple inheritance.

| Interfaces are also useful in their own right, since the notion of a
| stateless "supports" relationship is distinct from a class-based "is-a"
| relationship.
|| -- Barry
|
| --
| http://barrkel.blogspot.com/
Oh I see now. Thank you for your very fast response.

[Sericinus hunter]

Valmont wrote:

Moving from C++ to C# .Net:

Why does an interface exist in C# when I can create one by making all methods in
the abstract class "pure virtual"?
Did I miss something conceptually or is the "interface" just here for my
conveniance?

You cannot inherit from multiple classes in C#, but
you can implement multiple interfaces.