Javeed, note that that article says:

• In ADO the recordset can provide disconnected access
• To transmit data in ADO.NET, you use a dataset, which can transmit an XML stream

Therefore it is not accurate to say that ADO only works with connected data. Are you sure that it is not possible to use ADO .Net in a connected fasion? I am nearly sure that it is possible and therefore it is not accurate to imply that ADO is always disconnected. The article does however say that ADO is designed primarily for connected access.

It is also not accurate to say that "ADO.NET makes a copy of the data using XML" implying that it always uses XML. It is important to make it clear that ADO .Net does not always use XML; it supports XML but does not use it exclusively.

I think we all (except perhaps the person asking the question) agree that when using .Net, there is no reason to use ADO instead of ADO .Net. I think the answer should be that simple. There are many details about why ADO .Net is better but if .Net is used then there is no good reason to use ADO instead of ADO .Net. In fact, since ADO .Net does not use ActiveX, ADO .Net should be called something else.

here you go:

http://msdn.microsoft.com/en-us/library/904fck4k(v=vs.71).aspx

ADO was designed before .Net. ADO is ActiveX Data Objects; it is an ActiveX interface to databases. In the past, ActiveX was the latest and greatest technology; it was an improvement over more lower-level interfaces. ADO .Net is essentially ADO using .Net for the interface.

I am skeptical of most of the other differences that others say about ADO and ADO .Net. For example, ODBC is among the oldest of the technologies; it was first released in 1992. It has bulk operations such as the SQLBulkOperations Function, which provides the ability to process data in a disconnected way. ODBC and ADO have multiple types of recordsets therefore it is possible to "work on connected and disconnected manner" with them too.

If anyone has an authoritative comparison (such as an article in the MSDN) of ADO and ADO .Net then it would be more useful to have a link instead of copying and pasting the text.

Hi,

        What is ADO.NET? 

• ADO stands for ActiveX Data Objects
• ADO.NET is a database technology of .NET Framework used to connect application system and database server.
• ADO.NET is a part of the .NET Framework
• ADO.NET consists of a set of classes used to handle data access
• ADO.NET uses XML to store and transfer data among applications, which is not only an industry standard but also provide fast access of data for desktop and distributed applications.
• ADO.NET is scalable and interoperable.
  
  you may take a look at this Article :
  
  http://www.c-sharpcorner.com/UploadFile/puranindia/WhatisADONET07202009060504AM/WhatisADONET.aspx
  
  Difference between ADO and ADO.NET
  
  

  ADO	ADO.NET
  ADO has one main object that is used to reference data, called the RecordSet object.	ADO.NET provides objects that allow you to access data in various ways. The DataSetobject allows you to store the relational model of your database.  MARS (Multiple Active Result Sets) is implemented in ADO.NET
  You can only work on connected manner. This means that when you access data, such as viewing and updating data, it is real-time, with a connection being used all the time. This is barring, of course, you programming special routines to pull all your data into temporary tables.   In connected model you always get refreshed data.	ADO.NET uses data in a disconnected fashion. When you access data, ADO.NET makes a copy of the data using XML. ADO.NET only holds the connection open long enough to either pull down the data or to make any requested updates. This makes ADO.NET efficient to use for Web applications. It's also decent for desktop applications.   You can work on connected and disconnected manner.   In disconnected model you will get old data as you are editing it. Outlook is an example of disconnected model. We work on offline object model and when connection is required it is connected.   Connected object can be used on disconnected object.
  Whereas ADO allows you to persist records in XML format.	ADO.NET allows you to manipulate your data using XML as the primary means. This is nice when you are working with other business applications and also helps when you are working with firewalls because data is passed as HTML and XML.
  ADO allows you to create client-side cursors only.	ADO.NET gives you the choice of either using client-side or server-side cursors. In ADO.NET, classes actually handle the work of cursors. The developer has the freedom of choice in internetdevelopment, for creating efficient applications.

Hi Amit,

Please refer the below link

http://www.dotnetuncle.com/difference/2_ADO_ADONET.aspx


Thanks

Hi Amit,

You can find many articles in C# Corner with regards to ADO and ADO.NET, following are a few differences:

ADO works with connected data. This means that when you access data, such as viewing and updating data, it is real-time, with a connection being used all the time. This is barring, of course, you programming special routines to pull all your data into temporary tables.

ADO.NET uses data in a disconnected fashion. When you access data, ADO.NET makes a copy of the data using XML. ADO.NET only holds the connection open long enough to either pull down the data or to make any requested updates. This makes ADO.NET efficient to use for Web applications. It's also decent for desktop applications.

· ADO has one main object that is used to reference data, called the Recordset object. This object basically gives you a single table view of your data, although you can join tables to create a new set of records. With ADO.NET, you have various objects that allow you to access data in various ways. The DataSet object will actually allow you to store the relational model of your database. This allows you to pull up customers and their orders, accessing/updating the data in each related table individually.

· ADO allows you to create client-side cursors only, whereas ADO.NET gives you the choice of either using client-side or server-side cursors. In ADO.NET, classes actually handle the work of cursors. This allows the developer to decide which is best. For Internet development, this is crucial in creating efficient applications.

· Whereas ADO allows you to persist records in XML format, ADO.NET allows you to manipulate your data using XML as the primary means. This is nice when you are working with other business applications and also helps when you are working with firewalls because data is passed as HTML and XML.

Please do not forget to mark "Accepted Answer".