The innovation of DOTNET:LINQ and Ado.net 3.0

Ado

Do you know the major innovation and reform of Microsoft 's next Generation Ado.net 3.0 data access technology?

In order to allow you to preview the future of Ado.net 3.0 technology, although the priest has been busy in the ASP.net 2.0 publishing, but still can not afford to leave you to lead the new finger of the great purpose, and this is not you come to dotnet to develop the temple the biggest purpose? The priest roughly translated the United States Microsoft VP Somasegar Blog article, the first one weeks before he out of the thunder, burst red to the whole. NET Circle is quoting its article because it exposes the blueprint of the. NET Framework 3.0, the following is translation:

language-integrated Query (LINQ) is a breakthrough technology to eliminate uncoordinated resistance in different data areas, such as when querying XML, a related database, or an object, through LINQ technology, programmers do not need to learn individual query syntax, Since LINQ was announced last year in the PDC bulletin, and the Tech-ed Seminar in Boston this year, the use of LINQ has been very well received, and the next generation of visual Studio (Code Orcas) built LINQ Infrastructure combines the power of both language and APIs to support a variety of languages and data fields.

(The priest's vernacular note: This means that in the future, you can deal with SQL, XML, object, category queries with LINQ, and you can achieve a consistent query pattern through LINQ without having to prepare an individual syntax for every kind of data query, like my SQL is strong, but XML can be very basic, But LINQ can eliminate such deficiencies, and it is easy to achieve the same strong purpose. )

At this time the Ado.net Team Development Group has constructed a data Mapping technology called ado.net entities (O/R Mapping), Ado.net Entities promotes the entity structure of a linked table to a data model that can more precisely represent bussiness entities, such as "Customer" and order, and can mapping to multiple connected tables and views, You can imagine ado.net entities to specify the structure of the Bussiness object declaratively, and to join the business logic into the structure and query Bussiness object through powerful LINQ. Ado.net entities allows us to provide a common data model similar to the ado.net environment, and can be accessed by higher-order functions like reports, replication and BI, for the majority of the mainstream enterprise applications, ado.net Entities allows programmers to define complex, connected database Mapping (O/R Mapping) so that a new Bussiness object structure can be created without changing the schema at the bottom of the underlying database.

The above two major advances in data access programming will allow programmers to have more productivity, please view Anders Hejlsberg and Sam Druker recently in Channel 9 session.

We made a naming schema simplification so that you can easily identify these technologies:

　　* LINQ to ADO. NET includes the following:

LINQ to DataSet

LINQ to Entities

LINQ to SQL (previous dlinq)

　　*LINQ support for other types of data forms include:

LINQ to XML (previous xlinq)

LINQ to Objects

Our development team is working on the next generation of Visual Studio and implementing these technologies in a unified way so that programmers can have great development experience, we provide the LINQ May number here, and note the upcoming Entities Community preview in the end of this year.