Answer Posted / vikash kumar

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.

How can we perform data binding in atlas?

892

---

Define the mesi? : Dot net architecture

904

---

Define cache coherency and how is it eliminated? : Dot net architecture

910

---

What is difference between .net and visual studio?

934

---

What is the use of TPL DATAFLOW?

1005

---

Explain Singleton design pattern in .net

951

---

Explain the purpose of cache? : Dot net architecture

849

---

.Net Frame work arch?

2000

---

Explain about cookie less session state? : .NET Architecture

941

---

What is new in the .net 2.0 class library?

1070

---

12. Types of polymorphisem[Run and Design Exp.]

2021

---

What is the importance of updatepanel control?

992

---

How cache coherency is eliminated? : Dot net architecture

876

---

What is .net mobile utility controls. : Microsoft dot net mobile

941

---

What is .net mobile input validation. : Microsoft dot net mobile

897

---