Answer Posted / kvnvani

1. In ADO recordset(in memory representation of data) looks
like single table
where as
in ADO.NET dataset(in-memory representation of data) is a
collection of one or more tables(use JOIN Query).
2. In ADO you communicate with the database by making the
calls to an OLEDB Provider
where as
in ADO.NET you communicate with the database through a Data
Adapter(an OledbDataAdapter,SQLDataAdapter,OdbcDataAdapter
or OracleDataAdapter object) which make calls to an OLEDB
Provider or the API's provided by the underlying datasource.
3. In ADO recordset objects operate in a fully connected
state
where as
in ADO.NET dataset operate in disconnected state.
4. ADO requires COM marshalling to transmit records sets
among components, does require that ADO data types be
converted to COM data types.
where as
ADO.NET does not require data-type conversions.
5. In ADO it is sometime sproblematic firewalls( firewalls
are typically configured to allow HTML text to pass, but to
prevent system-level requests (such as COM marshalling)
from passing) prevent many types of requets
where as
in ADO.NET datasets using XML, firewalls can allow datasets
to pass.

Explain the use of view state?

1019

---

What is page request in asp.net?

961

---

What is session id in web application?

1101

---

What is the part of url?

987

---

Define what is razor? : asp.net mvc

1012

---

Define static member?

1001

---

Disable Mouse right click on web page in asp.net?

1051

---

What is state management in asp.net with example?

962

---

Any disadvantages in Dataset and in reflection ?

3260

---

What are the advantages of Web API?

1115

---

What is webresource axd?

885

---

Explain authorization levels in .net ?

1050

---

what are the ihttphandler and ihttphandlerfactory interfaces ?

945

---

List the events in page life cycle.

967

---

What is globalization and localization in asp net?

1002

---