| title | ms.custom | ms.date | ms.prod | ms.reviewer | ms.suite | ms.technology | ms.tgt_pltfrm | ms.topic | ms.assetid | caps.latest.revision | author | ms.author | manager | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
LINQ to DataSet |
03/30/2017 |
.net-framework |
|
article |
743e3755-3ecb-45a2-8d9b-9ed41f0dcf17 |
4 |
JennieHubbard |
jhubbard |
jhubbard |
LINQ to DataSet
[!INCLUDElinq_dataset] makes it easier and faster to query over data cached in a xref:System.Data.DataSet object. Specifically, [!INCLUDElinq_dataset] simplifies querying by enabling developers to write queries from the programming language itself, instead of by using a separate query language. This is especially useful for [!INCLUDEvsprvs] developers, who can now take advantage of the compile-time syntax checking, static typing, and IntelliSense support provided by the [!INCLUDEvsprvs] in their queries.
[!INCLUDElinq_dataset] can also be used to query over data that has been consolidated from one or more data sources. This enables many scenarios that require flexibility in how data is represented and handled, such as querying locally aggregated data and middle-tier caching in Web applications. In particular, generic reporting, analysis, and business intelligence applications require this method of manipulation.
The [!INCLUDElinq_dataset] functionality is exposed primarily through the extension methods in the xref:System.Data.DataRowExtensions and xref:System.Data.DataTableExtensions classes. [!INCLUDElinq_dataset] builds on and uses the existing [!INCLUDEado_whidbey_long] architecture, and is not meant to replace [!INCLUDEado_whidbey_long] in application code. Existing ADO.NET 2.0 code will continue to function in a [!INCLUDElinq_dataset] application. The relationship of [!INCLUDElinq_dataset] to [!INCLUDEado_whidbey_long] and the data store is illustrated in the following diagram.
In This Section
Reference
xref:System.Data.DataTableExtensions
xref:System.Data.DataRowExtensions
xref:System.Data.DataRowComparer
