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.

Why is this service branded with windows livetm?

1076

---

What are early binding and late binding.

1072

---

How to prepare culture-specific formatting in .net.

1023

---

What is xaml? Are xaml file compiled or built on runtime?

973

---

What is the file extension of web service?

993

---

How will you load dynamic assembly?

994

---

Explain about solution explorer window?

1029

---

What is a web farm?

986

---

Explain diff. Between friend and protected friend?

931

---

How can we create a website?

944

---

What is a page life cycle?

1045

---

What is difference between session and viewstate?

904

---

How can we pass info between 2 asp.net pages?

1075

---

What is the difference between the asp and asp.net?

985

---

What are custom controls?

945

---