Stir.NET consists of 2 primary area: A provider objects. These classes provide access to & communicate by owning the information source, like the SQL Server database. To for each one one information source has its have placed of provider objects, however it each have a green placed of postfix: -Connection: Will bring the connection to the information source, required to access it. As well acts as an abstract factory for command objects. -Command: Wont to perform a bit of action on the information source, like reading, updating, or even deleting relational information. -Parameter: Describes one parameter to the command. The most common lesson occurs as parameter to the stored procedure. -DataAdapter: The bridge utilized to transport information between the information source & the DataSet object (look at in the image below). -DataReader: An object utilized to expeditiously run the big listing of resolutions 1 record at once forgoing storing the children. the DataSet objects, the class action of classes describing a elementary inside-memory relational database. There exists simply of these, information-source-neutral, placed of DataSet objects, however two information & database schema structure may be imported from either more information sources sustaining -DataAdapter objects. the classes form a containment hierarchy: The DataSet object is an entire database. It may contain tables & relationships between people tables. The DataTable object is one table in the database. It has the title, rows, & columns. The DataColumn is the column of the table, including its title & nature and severity. The DataRow object is one row in the table, & allows reading & updating of the values in this row, likewise when retrieving any rows that come related to that across the primary-key foreign-key relationship. The DataRelation occurs as relationship between tables, like the primary-key foreign-key relationship. This is utile for enabling DataRow's functionality of retrieving related rows. the Constraint describes an implemented property of the database, like the singularity of the values within a primary key column. When information is modified any violations that arise may drive exceptions.

Functionality lives in the Visual Studio .NET IDE to create specialized subclasses of the DataSet classes for a particular database schema, allowing convenient access to each field through strongly-typed properties. This aids catch other software error at compile-period & makes a IDE's Intellisense feature more utile.

The utile discussion of the shift from either Fuss to Fuss.NET can be noticed in the MSDN article [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/adonetprogmsdn.asp ADO.NET for the ADO Programmer].

Sources of ADO.NET Providers
[http://msdn.microsoft.com/data/default.aspx?pull=/library/en-us/dnbda/html/daag.asp#daag_introducingadonet Microsoft] ships providers for two or three databases & a Bridge to ODBC drivers for have by using the Microsoft CLR, in Windows [http://www.datadirect.com/products/net/index.ssp DataDirect Technologies] ships 100% managed providers that come for the primary corporate databases (Oracle, Sybase, DB2, SQL Server) [http://uda.openlinksw.com/ado.net/ OpenLink Software] ships providers for even a total of target databases, including Bridges to more informatiin access mechanisms, for apply by using either the Microsoft or Mono CLR implementations, on Windows, Mack OS X, Solaris, Linux, & more platforms

de:ADO.NET it:ADO.NET