The ADO.NET Entity Framework is part of Microsoft’s next generation of .NET technologies. It is intended to make it easier and more effective for object-oriented applications to work with data.

2.  The ADO.NET Entity
Framework is part of
Microsoft’s next
generation of .NET
technologies.
 It is intended to make it
easier and more
effective for object-
oriented applications to
work with data.

3.  Originally intended to
be part of theVisual
Studio 2008 Release
 Now scheduled for
“later”.
 Entity Framework is
currently Beta 2
 Entity FrameworkTools
are currently CTP

4. Inherit differences between data expression in a relational database and
the same data expressed in an object-oriented application.

5. • Almost any business
application today has to
speak to a relational
database.
• This involves the usual
suspects of tables with
foreign keys, a
smattering of views,
and generally a gob of
stored procedures.

6.  Applications
themselves are written
in a completely
different world.
 The same data that
lives in the relational
database is represented
entirely differently in
the application.

7.  The result of this
“impedance mismatch”
is that developers
devote a lot of time and
energy writing code to
translate between how
the database likes to
see data and how the
application likes to see
data.

8.  Hibernate (Java)
 Enterprise Objects Framework (Mac OS)
 NHibernate (.NET)
 LINQ to SQL (Visual Studio 2008)
 And many, many, more …

9.  The ADO.NET Entity
Framework seeks to
remedy the problem by
providing a layer of
abstraction between
the logical data model
and the application
domain.

10.  Closer to the application
problem space
 Better suited for object
oriented programming
 Supports Inheritance
 Supports complex types
 Relationships are more
meaningful to the
application

11. The tools and technology that developers will interact with when using
the ADO.NET Entity Framework

12.  A gob of XML that
defines
 Logical DataTables,
Views, Foreign Keys
 Entity Objects that Map
to the Logical Data
 The Mapping Between
theTwo

13.  AVisual Studio
Designer that protects
developers from the
XML that is the EDM

14.  A code-generated data
context created from
the Entity Data Model
 Responsible for
managing
communication
between the conceptual
data model and the
logical data model

15.  Code-generated class
definitions for objects
defined in the EDM.

16.  A brand new SQL language
to learn
 Leverages the rich, object-
oriented Entity Data Model
 Inheritance
 Collections
 ComplexTypes
 Literal Strings – No
Compiler Checking
 Questionable value in
embedded SQL in code

17.  Queries the object
model created against
the EDM
 Still string-based. No
compiler checking
 An ugly mix of code and
eSQL statements

18.  Full compiler checking.
No wondering if the
query is valid.
 A fun new SQL-Like
syntax
 More OO-ish

19. Database TablesDatabase Tables Entity Data ModelEntity Data Model

20. Database TablesDatabase Tables Entity Data ModelEntity Data Model