Answer Posted / ramani krunal

1. interface contains methods that must be abstract;
abstract class may contain concrete methods.
2. interface contains variables that must be static and
final; abstract class may contain non-final and final variables.
3. members in an interface are public by default,
abstract class may contain non-public members.
4. interface is used to "implements"; whereas abstract
class is used to "extends".
5. interface can be used to achieve multiple inheritance;
abstract class can be used as a single inheritance.
6. interface can "extends" another interface, abstract
class can "extends" another class and "implements" multiple
interfaces.
7. interface is absolutely abstract; abstract class can
be invoked if a main() exists.
8. interface is more flexible than abstract class because
one class can only "extends" one super class, but
"implements" multiple interfaces.
9. If given a choice, use interface instead of abstract
class.

What are the different pipelining hazards? : Dot net architecture

1066

---

Difference between throw exception and rethrowing ?

2154

---

Can you Explain element .net mobile with example? : Microsoft dot net mobile

989

---

What is the difference between absolute expiration and sliding-time expiration?

1088

---

What is a clickonce application?

975

---

How to implement the display in the class printdoc (how to resolve the naming conflict) a: no naming conflicts

1108

---

question related to table havi colspan and row span

2312

---

Define an interrupt? : Dot net architecture

1023

---

What's the difference between an application and a program?

1227

---

Explain dma? : Dot net architecture

1067

---

What is difference between Desktop, Client Server & Web based applications?

1093

---

What is difference between .net and visual studio?

1023

---

What does this do? Gacutil /l | find /i "corillian"

1074

---

How do I write to the application configuration file at runtime?

1056

---

Are there any third party logging components available?

991

---