ADO.NET is made of a set of classes that are used for connecting to a database, providing access to relational data, XML, application data, and retrieving results. ADO.NET includes .NET Framework data providers for connecting to a database, executing commands, and retrieving results. Those results are either processed directly, or placed in an ADO.NET DataSet object
The ADO.NET classes are found in System.Data.dll, and are integrated with the XML classes found in System.Xml.dll. When compiling code that uses the System.Data namespace, reference both System.Data.dll and System.Xml.dll
Differance between ADO and ADO.NET
I’ve just introduces something Microsoft calls ADO.NET. Don’t confuse this new .NET data access interface with what we have grown to know and understand as ADO—I think it’s really very different. Yes, ADO.NET and ADO both open connections and fetch data, however, they do so in different ways using different objects and with different limitations. No, they aren’t the same—no matter what Microsoft names them. Yes,
ADO.NET has a Connection object, Command object, and Parameter objects (actually implemented by the SqlClient, OleDb and Odbc .NET Data Providers), however, they don’t have the same properties, methods, or behaviors as their ADOc counterparts.
1. This object model could be used even for non RDBMS products. We can read data from xml excel files also.
2. ADO objects are dependent on OLEDB providers and OLEDB providers would connect to the back end.
3. Fully COM based.
1. It is not an enhanced version of ADO. Its a new object model which has some objects similar to ADO.
2.In ADO.NET we use Managed Providers.