Posted by : Rhyf Ahmad Thursday, May 21, 2015

ADO.NET 1.x was the successor to ActiveX Data Objects 2.6 (ADO). The goal of ADO. NET 1.x was to enable developers to easily create distributed, data-sharing applications in the .NET Framework. The goals of ADO.NET today are to improve the performance of existing features in ADO.NET 1.x, to provide easier use, and to add new features without breaking backward compatibility.
ADO.NET 1.x was built upon industry standards such as XML and XSD, and it provided a data-access interface to communicate with data sources such as SQL Server and Oracle. ADO .NET 4.5 continues to build upon these concepts, while increasing performance. Applications can use ADO.NET to connect to these data sources and retrieve, manipulate, and update data. ADO. NET 4.5 does not break any compatibility with ADO.NET 2.0 or 1.x; it only adds to the stack of functionality.
In solutions that require disconnected or remote access to data, ADO.NET uses XML to exchange data between programs or with Web pages. Any component that can read XML can make use of ADO.NET components. A receiving component does not even have to be an ADO.NET component if a transmitting ADO.NET component packages and delivers a data set in an XML format. Transmitting information in XML-formatted data sets enables programmers to easily separate the data processing and user interface components of a data-sharing application onto separate servers. This can greatly improve both the performance and the maintainability of systems that support many users.
For distributed applications, ADO.NET 1.x proved that the use of XML data sets provided performance advantages relative to the COM marshaling used to transmit disconnected data sets in ADO. Because transmission of data sets occurred through XML streams in a simple text-based standard accepted throughout the industry, receiving components did not require any of the architectural restrictions required by COM. XML data sets used in ADO.NET 1.x also avoided the processing cost of converting values in the Fields collection of a Recordset object to data types recognized by COM. Virtually any two components from different systems can share XML data sets, provided that they both use the same XML schema for formatting the data set. This continues to be true in ADO.NET 4.5, but the story gets better. The XML integration in ADO.NET today is even stronger, and extensive work was done to improve the performance of the DataSet object, particularly in the areas of serialization and memory usage.


ADO.NET Architecture
Basic ADO.NET Features
  1. Common ADO.NET Tasks
  2. Basic ADO.NET Namespaces and Classes
  3. ADO.NET Components

.NET Data Providers
  1. Connection Object
  2. Command Object
  3. Using Stored Procedures with Command Objects
  4. DataReader Object
  5. Executing Commands Asynchronously
  6. DataAdapter Objects
  7. SQL Server .NET Data Provider
  8. OLE DB .NET Data Provider

The DataSet Component
  1. DataTableCollection
  2. DataRelationCollection
  3. ExtendedProperties
  4. Creating and Using DataSet Objects
  5. ADO.NET DataTable Objects
  6. Advanced ADO.NET Features of the DataSet and DataTable Objects

Working with the Common Provider Model
Connection Pooling in ADO.NET
Transactions and System.Transactions
  1. Creating Transactions
  2. Creating Resource Managers 

Ebook Preview
Get the ebook now (520 kB)

If the link above doesn't work, try the link below

Mirror: Get the ebook now (520 kB)

Leave a Reply

You can leave a comment to request any article(s), software(s), ebook(s) or report the dead link.
Then I will reply as soon as I can :)

Subscribe to Posts | Subscribe to Comments

Welcome to My Blog

Recent Post

Recent Posts Widget

- Copyright © Madriva -Robotic Notes- Powered by Blogger - Designed by Johanes Djogan -