Answer Posted / matt s

An interface definition specifies the 'intent' of a public
interface without forcing a base implementation. It's more
used (in favour of base or abstract classes) in cases where
the interface defines some common 'high level'
characteristics or concepts for completely different
implementations - e.g:

A 'dog' interface may be specified with common methods such
as 'scratch' and 'bark', but each type of dog's
implementation of those would be completely different.
It's still a useful design feature however as it recognises
there are similarities at the higher 'behaviour' level.

How do I declare inout arguments in c#?

887

---

What is the main purpose of delegates in c#?

916

---

What are the 2 broad classifications of fields in c#?

888

---

How to reverse each word in a string using c#?

1000

---

Can we maintain state in webservice?

917

---

What's the difference between abstraction and encapsulation?

846

---

What do you mean by stack and heap in c#?

860

---

Explain the difference between “as” and “is” operators used in c#?

909

---

Define collections?

879

---

Is c# different than c++?

836

---

What is collection class c#?

858

---

What are generic types?

885

---

What is wrong with the sample program below?

901

---

Is nullable type c#?

878

---

Show us in simple steps to create setup & deployment project for windows application?

925

---