ADO.NET consists of a data set of Objects. That describe data access services to the .NET environment and it is a data access technology. The Data access technology provide from Microsoft .Net Framework. Which is provides communications in between relational and non-relational systems through a common data set of components.
System, data, namespaces, etc. is the core of ADO.NET. It contains classes use by all data providers. Easily use for ADO.NET is designed. Microsoft Visual Studio is provides several wizards, also provides other features that you can use togenerate ADO.NET data access code. The two key components of ADO.NET are Data Providers and Dataset. The Data Provider classes are meant to work with different kinds of data-sources. They are used to perform all task data-management operations on specific databases.
Class of dataset provides mechanisms for managing data when it is lost connection from the data source. The .Net Framework includes main three data providers for ADO.NET. They are providing specific of the Microsoft SQL server Data provider Object Linking and Embedding, Database Data provider and ODBC Data provider. SQL Server most uses the SqlConnection object, OLEDB uses the Ole-DB Connection Object and ODBC uses OdbcConnection Object respectively.
A data or dataset provider contains Command, Connection, Data Adapter and Data Reader objects. These objects provide the functionality of Data providers in the ADO.NET. The Connection of Object provides physical connection to the Data Source. Connections of objects need the compulsory information to recognize the data source and to log on to it properly. This information is provided through a connection string in ADO.NET.
LINQ to DataSet provides queries capabilities. LINQ compile-time type checking over data cached in a DataSet object. It’s allows you to write query in one of the .NET Framework. They are such as C# or Visual Basic.
LINQ to SQL supports queries against an object model. That is way to the DS of a relational DB without using an intermediate conceptual model. Each table is represented by a separate class and tightly coupling the object model to the relational database schema (RDB). LINQ to SQL translates in machine level language-integrated queries in the object model into Transact-SQL and send them to the database for compile and execution. When the database returns the results or values, LINQ to SQL translates the results back into objects.
ADO.NET and the Extensible Markup Languageclasses in the .NET Framework area in the DataSet object. The DataSet can be popular with data from an Extensible Markup Language source. Whether it is a file or an XML stream. The DataSet can be written as World-Wide Web Consortium (W3C) compliant XML that includes its schema as XML schema definition language (XSD) schema, regardless of the source of the data in the DataSet. Because of the native serialization format of the DataSet is XML, it is an excellent medium for moving data between tiers, making the DataSet an optimal choice for remoting data and schema context to and from an XML Web service. For more information, see XML Documents and Data.