Your SlideShare is downloading. ×
 The ADO.NET Entity
Framework is part of
Microsoft’s next
generation of .NET
technologies.
 It is intended to make it
ea...
 Originally intended to
be part of theVisual
Studio 2008 Release
 Now scheduled for
“later”.
 Entity Framework is
curre...
Inherit differences between data expression in a relational database and
the same data expressed in an object-oriented app...
• Almost any business
application today has to
speak to a relational
database.
• This involves the usual
suspects of table...
 Applications
themselves are written
in a completely
different world.
 The same data that
lives in the relational
databa...
 The result of this
“impedance mismatch”
is that developers
devote a lot of time and
energy writing code to
translate bet...
 Hibernate (Java)
 Enterprise Objects Framework (Mac OS)
 NHibernate (.NET)
 LINQ to SQL (Visual Studio 2008)
 And ma...
 The ADO.NET Entity
Framework seeks to
remedy the problem by
providing a layer of
abstraction between
the logical data mo...
 Closer to the application
problem space
 Better suited for object
oriented programming
 Supports Inheritance
 Support...
The tools and technology that developers will interact with when using
the ADO.NET Entity Framework
 A gob of XML that
defines
 Logical DataTables,
Views, Foreign Keys
 Entity Objects that Map
to the Logical Data
 The ...
 AVisual Studio
Designer that protects
developers from the
XML that is the EDM
 A code-generated data
context created from
the Entity Data Model
 Responsible for
managing
communication
between the co...
 Code-generated class
definitions for objects
defined in the EDM.
 A brand new SQL language
to learn
 Leverages the rich, object-
oriented Entity Data Model
 Inheritance
 Collections
...
 Queries the object
model created against
the EDM
 Still string-based. No
compiler checking
 An ugly mix of code and
eS...
 Full compiler checking.
No wondering if the
query is valid.
 A fun new SQL-Like
syntax
 More OO-ish
Database TablesDatabase Tables Entity Data ModelEntity Data Model
Database TablesDatabase Tables Entity Data ModelEntity Data Model
ADO.NET Entity Framework
Upcoming SlideShare
Loading in...5
×

ADO.NET Entity Framework

1,673

Published on

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.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,673
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
6
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Transcript of "ADO.NET Entity Framework"

  1. 1.  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. 2.  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
  3. 3. Inherit differences between data expression in a relational database and the same data expressed in an object-oriented application.
  4. 4. • 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.
  5. 5.  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.
  6. 6.  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.
  7. 7.  Hibernate (Java)  Enterprise Objects Framework (Mac OS)  NHibernate (.NET)  LINQ to SQL (Visual Studio 2008)  And many, many, more …
  8. 8.  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.
  9. 9.  Closer to the application problem space  Better suited for object oriented programming  Supports Inheritance  Supports complex types  Relationships are more meaningful to the application
  10. 10. The tools and technology that developers will interact with when using the ADO.NET Entity Framework
  11. 11.  A gob of XML that defines  Logical DataTables, Views, Foreign Keys  Entity Objects that Map to the Logical Data  The Mapping Between theTwo
  12. 12.  AVisual Studio Designer that protects developers from the XML that is the EDM
  13. 13.  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
  14. 14.  Code-generated class definitions for objects defined in the EDM.
  15. 15.  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
  16. 16.  Queries the object model created against the EDM  Still string-based. No compiler checking  An ugly mix of code and eSQL statements
  17. 17.  Full compiler checking. No wondering if the query is valid.  A fun new SQL-Like syntax  More OO-ish
  18. 18. Database TablesDatabase Tables Entity Data ModelEntity Data Model
  19. 19. Database TablesDatabase Tables Entity Data ModelEntity Data Model

×