Most applications are currently written on top of relational databases. At some point, these applications will have to interact with the data represented in a relational form. Database schemas are not always ideal for building applications, and the conceptual models of applications differ from the logical models of databases. The Entity Data Model (EDM) is a conceptual data model that can be used to model the data of a particular domain so that applications can interact with data as entities or objects. For more information, see Entity Data Model.
許多應用程式經常基于一個關系型資料庫來編寫。在有些時候，這些應用程式将不得不和以關系方式提供的資料相比配。在編寫應用程式時，資料架構通常不是一下子就很理想的，并且應用程式的概念模型和資料庫的邏輯邏輯模型是不一緻的。實體資料模型(EDM)是一種概念資料模型，能被用來對特定的領域進行資料模組化。是以應用程式能和作為實體或對向的資料相比對。更多資訊請參考實體資料模型。
Through the EDM, ADO.NET exposes entities as objects in the .NET environment. This makes the object layer an ideal target for Language-Integrated Query (LINQ) support. Therefore, LINQ to ADO.NET includes LINQ to Entities. LINQ to Entities enables developers to write queries against the database from the same language used to build the business logic. The following diagram shows the relationship between LINQ to Entities and the Entity Framework, ADO.NET 2.0, and the data store.
通過使用EDM，ADO.NET在 .net 環境中以對象的方式公開實體。這使得對象層成為內建語言查詢(LINQ)的一個理想的操作目标。是以，ADO.net-LINQ 包括了實體LINQ。實體LINQ支援開發人員使用和編寫業務邏輯相同的語言來編寫基于資料庫的查詢。下圖展示了實體LINQ、實體架構、ADO.NET 2.0以及資料庫之間的關系
For LINQ to Entities sample applications, see Data Access and Storage. For information about late breaking changes in the ADO.NET Entity Framework and LINQ to Entities, see the ADO.NET team blog.
Getting Started (LINQ to Entities)/入門（實體LINQ）
Programming Guide (LINQ to Entities)/程式設計指南（實體LINQ）
Reference (LINQ to Entities)/參考（實體LINQ）
Language-Integrated Query (LINQ)
LINQ to ADO.NET
<a href="http://www.cnblogs.com/Chinese-xu/archive/2007/09/20/899916.html">ADO.NET Entity Framework/ADO.NET 實體架構</a>
本文版權歸作者和部落格園共有，歡迎轉載，但未經作者同意必須保留此段聲明，且在文章頁面明顯位置給出原文連接配接。
本文轉自徐少俠部落格園部落格，原文連結：http://www.cnblogs.com/Chinese-xu/archive/2007/09/21/900876.html，如需轉載請自行聯系原作者