精通ADO.NET Entity Framework 4.0

5星 · 超过95%的资源需积分: 10 111 浏览量更新于2024-07-31 收藏 18.77MB PDF 举报

"Apress.Pro.Entity.Framework.4.0.pdf" 本书《Pro Entity Framework 4.0》由Scott Klein撰写，是.NET编程领域的一本专业书籍，专注于探讨ADO.NET Entity Framework 4.0的使用和应用。Entity Framework是一个对象/关系映射（ORM）框架，它允许开发者以强类型对象的形式处理关系数据，从而减少了在许多现代应用程序中常见的大量数据访问代码。 Entity Framework 4.0引入了许多改进和新特性，使得开发人员能够更高效地设计和开发应用程序。本书通过介绍与Visual Studio 2010的结合使用，展示了如何利用这些新功能构建基于Windows和WCF Data Services的应用程序。作者首先对Entity Framework进行概述，强调其核心特性，如Entity Data Model。Entity Data Model是Entity Framework的核心，它定义了应用程序与数据库之间的数据结构。书中详细讲解了Entity Data Model的内部机制，使读者了解如何利用这些机制来创建灵活的应用。书中的一个重要部分是关于使用LINQ（Language Integrated Query）查询Entity Data Model的内容。LINQ是.NET Framework的一部分，它允许开发者使用类似SQL的语法在代码中直接进行数据查询。通过“LINQ to Entities”，开发者可以方便地在实体模型上执行复杂的数据库查询，大大简化了数据操作。此外，书中还涵盖了Entity Framework 4.0的新特性，例如： 1. **Code First**：这是一种新的开发模式，允许开发者通过编写C#或VB.NET代码来定义模型，然后自动生成数据库结构，简化了数据库和应用程序模型的同步。 2. **Poco支持**：支持Plain Old CLR Objects（Poco），这意味着实体类可以不依赖于Entity Framework特定的基类或接口，增强了代码的可移植性和灵活性。 3. **自定义关系映射**：允许开发者更精细地控制数据模型与数据库表之间的映射，包括列、键、索引和关系的映射。 4. **Change Tracking**：Entity Framework提供了强大的变更跟踪机制，自动检测对象状态的变化，并在需要时将这些变化持久化到数据库中。 5. **异步操作**：Entity Framework 4.0引入了异步API，使得在处理大量数据或执行长时间运行的查询时，可以避免阻塞应用程序的UI线程，提高了用户体验。 6. **性能优化**：针对性能进行了改进，包括缓存策略、查询优化以及更好的批处理能力，使得在大数据量场景下，Entity Framework的性能得到提升。通过深入阅读本书，开发者将获得关于Entity Framework 4.0的全面理解，能够熟练地运用这个强大的工具来构建高效、可维护的.NET应用程序。

C H A P T E R 1

■ ■ ■

Introducing the ADO.NET 4.0

Entity Framework

In July 2008 Microsoft released the first version of the ADO.NET Entity Framework as part of the Visual

Studio 2008 Service Pack 1 as well as the .NET Framework 3.5 Service Pack 1. At the time, Microsoft LINQ

(Language Integrated Query) and LINQ to SQL had been out for a while and were gaining a lot of

attention. Both the Entity Framework and LINQ to SQL showed that Microsoft was very serious about

improving developer productivity, by providing an infrastructure for managing relational data as objects

and programming against a conceptual model instead of directly against a storage schema. While

Microsoft did its best to tout the Entity Framework, it went somewhat unnoticed out of the gate,

primarily due to the rise in popularity of LINQ to SQL and the misunderstanding from the public of what

the Entity Framework really was.

By the time this book hits the shelves, Visual Studio 2010 with the .NET Framework 4.0 and

ADO.NET Entity Framework will have just been released or will be very shortly. Yet, I still get questions

from people wondering what the Entity Framework is or how it differs from LINQ to SQL.

Thus, the reason for this book is twofold; first, it will answer the question of what the Entity

Framework is and why Microsoft is dedicating a lot of resources and energy to its development,

advancement, and developer acceptance. Second, it will discuss all the new features and enhancements

that will be available in ADO.NET 4.0, which will be released with Visual Studio 2010.

This book is intended to address two types of developers: those who have never worked with the

Entity Framework before, and those who have but are looking at what the ADO.NET 4.0 Entity

Framework has to offer. As such, it will cover all aspects of the Entity Framework and, where

appropriate, point out the new features and enhancements found in the EF 4.0.

The Entity Framework does not, nor is intended to, replace existing ADO.NET data access

technologies; rather, it is an enhancement to ADO.NET, providing developers an augmented approach

to accessing data, letting them work with a conceptual model, and thus enabling developers to deal with

data as objects and properties, a concept already familiar to them.

The Need for an Entity Framework

To really understand what the Entity Framework is and why it is so important, we need to take a step

back and look at some of the existing data access technologies. Microsoft has put a lot of time and effort

into ADO.NET over the past many years. Prior to that, it was RDO, and prior to that it was DAO. Heaven

forbid we look prior to DAO. With ADO.NET, developers were finally sensing that Microsoft had settled

on a data access strategy and technology. With the improvements and enhancements that were being

made to ADO.NET with each .NET release, it was the “go-to” technology for data access.

Developers’ data access technologies of choice have primarily been the DataReader and the DataSet,

and these have been serving developers well for many years. Yet with all of the improvements being

made to ADO.NET, there was still a disconnect between the application and the back-end database.

CHAPTER 1

■

INTRODUCING THE ADO.NET 4.0 ENTITY FRAMEWORK

Developers were spending far too much time trying to keep up with changes being made to the

database. Any schema change to a table or stored procedure, for example, could potentially break an

application.

Take the following code snippet, for example, which runs against Microsoft’s standard

AdventureWorks example database. Take a good look at this code sample and then ask yourself two

questions:

1. Will it compile?

2. Assuming it compiles, when it runs, will you get the “yep, we have rows”

message?

try

{

string connectionString = Class1.GetConnectionString();

using (SqlConnection conn = new SqlConnection(connectionString))

{

conn.Open();

using (SqlCommand cmd = new SqlCommand())

{

cmd.Connection = conn;

cmd.CommandText = "SELECT FirstName, MidleName, LastName FROM Person.Contact

WHERE ContactID = @ContactID";

SqlParameter param = new SqlParameter("@ContactID", SqlDbType.Int, 50,

"ContactID");

param.Value = 8;

cmd.Parameters.Add(param);

SqlDataReader rdr = cmd.ExecuteReader();

while (rdr.Read())

{

Console.WriteLine(String.Format("{0}, {1}",

rdr[0], rdr[1]));

}

catch (Exception ex)

{

MessageBox.Show(ex.Message);

}

If you want to try it out, open up a new instance of Visual Studio 2010 (or 2008—this example is not

specific to 2010) and create a new C# Windows Forms application. On the form, place a button on the

form and in the click event of that button enter the code as you see it above. Prior to running the project,

change the connection string username and password for your environment and add the following using

statement:

using System.Data.SqlClient;

If you don’t feel like typing, you can download the code from the Apress web site for this book. In

any case, run the project and click the button. When the project runs and the form displays, it should be

CHAPTER 1

■

INTRODUCING THE ADO.NET 4.0 ENTITY FRAMEWORK

obvious at that point that the code did compile successfully. Now click the button. Did you get the “yep,

we have rows” message?

If you typed in the code just as you see it above, you didn’t get the message indicating a successful

run. Instead you received a message that the column MidName is an invalid column name. The column

containing the middle name is actually called MiddleName. The problem is you had to run the

application to find that out. Now imagine if yours had been a larger production application and you

received a similar error. A larger application makes it much more difficult to find the offending line of

code, plus you have the greater overhead of tracking down the actual spelling of the column name.

The point is that developers spend far too much time worrying about things they shouldn’t need to

when it comes to the database side of things. Developers need to focus only on developing applications

and should not be concerned if a table, stored procedure, relationship, or some other database object

changes.

In the code example above, the error that you get illustrates an example of a table change being

made without informing the developers. When the table was originally created, it possibly could have

had a column named MidName, but someone decided to change that column’s name to MiddleName to be

consistent with the other name columns in the table. Unless that schema change is disseminated to the

appropriate people (the developers in this case), no one is going to find out about the change until run

time. Think of what could happen if for some reason the change was not picked up and somehow

slipped through QA and into the production release. Oops.

What was needed was a model where the database, application, and data move together. This is

exactly what the Entity Framework provides. The Entity Framework is a conceptual model that works

with databases and applications, eliminating the gap between data and applications (and application

languages) that developers normally have to work with when working with the DataReader object and

other data access technologies.

This Has Been Tried Before

Modeling applications exist in abundance, but each application has a specific focus such as process data

flow or describing objects. The following lists some of the modeling application types and their primary

focus.

• ERM (Entity Relationship Model): Used with databases, it is a way to represent

logical relationships of entities (objects) in order to create a database.

• UML (Unified Modeling Language): A standard modeling language that is used to

describe objects.

• ORM (Object-Relational Mapping): Method of mapping relational databases and

object-oriented programming languages.

• DFD (Data Flow Diagram): A graphical representation of the flow of data between

processes and between systems.

The problem is that each of these modeling applications is limited in scope. For example, ERM

products do logical data models really well, but struggle at UML tasks. UML excels at describing objects,

but falls short at performing ERM tasks.

And lest we forget, there are other ERM-like products in the market that have been around for a bit

and provide Entity Framework-like capabilities, such as the following:

• NHibernate: Ported from Hibernate Core for Java for the .NET Framework,

NHibernate for .NET persists plain .NET objects to and from an underlying

relational database.

CHAPTER 1

■

INTRODUCING THE ADO.NET 4.0 ENTITY FRAMEWORK

• SPRINT.net: An open-source application framework, and based on the Java

version of Spring Framework, allowing you to build components that can be

integrated into multiple tiers of your application.

While this list is by no means complete, it is provided to illustrate the necessity and need for good

ERM application development products that remove many of the complexities of working with

databases to help improve productivity.

The ADO.NET Entity Framework does not have the same limitations of other modeling products.

This is because the Entity Framework works at a conceptual level that is based on the ERM and, as such,

provides a depth and richness of functionality that many of the stand-alone ERMs and UMLs cannot

provide.

As the name suggests, the Entity Framework allows you to work directly with Entities that represent

your own schema without having to deal with the nuances of DataReader and DataSet objects. Some

developers who have worked with or have some knowledge about Entity Framework compare it to other

relational mappers and try to classify it as an object relational mapper. This comparison or thought

process is not entirely correct. The Entity Framework does have relational mapping capabilities. But the

Entity Framework is much more than just a relational mapper, and the ORM capabilities it does have are

implemented much differently than that of other ORM products.

So, What Is the Entity Framework?

The Entity Framework is a set of technologies in ADO.NET that helps fill in the space between object-

oriented development (objects) and databases. This gap is commonly known as an “impedance

mismatch” and it exists because the mapping and organization of classes does not quite match up to the

organization of relational objects. Many mapping solutions have tried to solve this problem by mapping

OO (object-oriented) classes and properties straight to tables and columns.

For example, let’s use the case of customers and products. First, in a simple mapping scenario, you

may have a product class that contains a property that references an instance of a customer class.

Second, a customer class might contain a property containing a collection of instances of the product

class. While this might seem fine, how do you represent the foreign keys between customer and product

in the first case (while in the second case you have a reference of an object-oriented collection of

product instances that has no comparable column in the customer table in the database)?

A scenario such as this one is known as the conceptual space and is accomplished by raising the

abstraction level to a point that lets developers query entities and relationships in the conceptual model,

all while letting the Entity Framework translate the query operations to data source–specific commands.

It allows applications to be written against conceptual models and not directly against the database. By

doing so, the gap between object-oriented programming and databases has been closed, letting

developers focus on the task of developing applications, without concerning themselves about the

database (structure or otherwise) or data access.

You should start to see where the gap comes into play, simply because there is no one-to-one

mapping. Relationships between relational objects are represented much differently from class

relationships. And this is where the Entity Framework takes a much different approach. The EF maps

relational objects to conceptual models. Conceptual mapping provides a number of huge benefits. For

example, it provides the needed improved flexibility in creating (defining) and enhancing the logical

model.

■ Note The Entity Framework divides the data model into three separate models: conceptual, logical, and

physical. Each of these will be discussed in detail in Chapter 3.

剩余280页未读，继续阅读

s65976012

粉丝: 1
资源: 4

精通ADO.NET Entity Framework 4.0

Entity framework pdf

Entity Framework实用精要.pdf (吕高旭)

Entity Framework 6 ASP.NET MVC 5项目实战.pdf

Apress.Pro.Entity.Framework.4.0.Mar.2010.rar

Apress.Pro.Dynamic.NET.4.0.Applications.Jan.2010

Apress.Pro.Dynamic.dot.NET.4.0.Applications.Jan.2010

Apress.Pro.Entity.Framework.Core.2.for.ASP.NET.Core.MVC.2018

[Apress.J2EE系列].Apress.Pro.JSP.2.4th.Edition.Dec.2005

《Apress.Pro.ASP.NET.MVC.3.Framework》PDF版

Apress.Pro.JSF.and.Ajax.pdf

最新资源