Entity Framework 4 In Microsoft Visual Studio 2010 - ericnel
Upcoming SlideShare
Loading in...5

Like this? Share it with your network


Entity Framework 4 In Microsoft Visual Studio 2010 - ericnel

Uploaded on

Session on Entity Framework 4 in Visual Studio 2010 delivered at www.dotnetdevnet.com in Bristol on 3rd Dec.

Session on Entity Framework 4 in Visual Studio 2010 delivered at www.dotnetdevnet.com in Bristol on 3rd Dec.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 216

http://blogs.msdn.com 112
http://www.slideshare.net 67
http://geekswithblogs.net 37

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide
  • LLBLGen Pro http://www.llblgen.com/Nhibernatehttp://www.hibernate.org/343.htmlEntitySpaceshttp://www.entityspaces.net/Portal/Default.aspxOpen Access http://www.telerik.com/products/orm.aspxDevForcehttp://www.ideablade.com/XPO http://www.devexpress.com/Products/NET/ORM/Lightspeedhttp://www.mindscape.co.nz/products/LightSpeed/default.aspxPlus many, many moreOf 31 .NET ORMs in 2003, 9 lasted to 2008
  • Code GenIn V1 we had EntityClassGenerator which could be configured using eventsHard (it used CodeDom)Inflexible (not much control)In V2 we will haveTemplatedEntityClassGenerator and will ship default T4 templatesCustomization via ToolsUses Workflow FoundationComplex typesPluralizationPublic abstract PluralizationServiceDefault implementation is English OnlyDefault rules:EntityTypes / ComplexTypes are singularizedEntitySets are pluralizedNavigation Properties based on cardinalityStored ProceduresStored Procedures as functionsMapping support for stored procedure resultComplex type as return typeScalar and void return typeEntity CUD using Stored ProceduresNo need to have SPs for all CUD
  • Foreign KeysIndependent Association – v1 Product p = new Product { ID = 1,       Name = "Bovril",       Category = context.Categories                        .Single(c => c.Name == "Food") }; context.SaveChanges(); FK Association – v2 Product p = new Product     {         ID = 1,         Name = "Bovril",         CategoryID = 13     };     context.Products.AddObject(p);     context.SaveChanges();Deferred LoadingCan do lazy loadContext.deferredloading=true Model Level using ESQL<Function Name=“CustomerFullName” ReturnType=“String”><Parameter Name=“customer” Type=“MyModel.customer”> <DefiningExpression>customer.FirstName + ‘ ‘ + customer.LastName </DefiningExpression> </Function>Enables from c in ctx.Customers select c.FullName()CLR Level [EdmFunction("MyModel", "CustomerFullName")] public static string FullName(this customer c) { return String.Format("{0} {1}", c.FirstName, c.LastName); }Enables Console.WriteLine(c.FullName());Inline Functions in ESQL using Northwind;function AmountPurchased(c Customer) as Sum (c.Sales.Amt)function AmountReturned(c Customer) as Sum (c.Returns.Amt)function AmountConsumed(c Customer) as                                                                     AmountPurchased(c) – AmountReturned(c)select AmountConsumed(c) from Customers as c;
  • Code OnlyNo XML files, no model!Convention to configE.g. Convention: xxxID to a primary key, schema=dboE.g. Config: On map to schema sys and class property to table column[TableMapping(Schema=“sys”,TableName=“MyDBTable”][ColumnMapping(PropertyName=“MyClassProp1”, ColumnName=“table_column1”)][Key(PropertyName=“MyClassProp1”)]public objectset<MyThing> MyThings...


  • 1. ADO.NET Entity Framework in Microsoft Visual Studio 2010 and Microsoft .NET Framework 4
    Eric Nelson
    (or http://bit.ly/ericnelson )
    Developer Evangelist
    Microsoft UK
  • 2. Were you on twitter last Dec?http://twitter.com/ericnel
  • 3. Agenda
    Quick recap of the journey so far
    Entity Framework 4.0 Drill Down
    Lots of demos
  • 4. Object Relational Mapping
    Many ORMs out there
    No clear “winner” = relatively little adoption of ORM
    Developers waiting on Microsoft
    Then we shipped two ... hmmm
    LINQ to SQL in Visual Studio 2008
    ADO.NET Entity Framework in Visual Studio 2008 SP1
  • 5. ADO.NET Entity Framework Recap
    Entity Data Model
    Tools and services to create an Entity Data Model (EDM)
    Conceptual to Mapping to Storage
    Tools and services for consuming an Entity Data Model
    LINQ to Entities, Object Services and Entity SQL
    Together they address the “impedance mismatch”
    Objects in
    Rows in
  • 6. Entity Framework 1.0Too many pain points
    The designer!
    Model First not supported
    Poor support for Stored Procedures
    No Pluralization/Singularization
    Foreign Keys hidden
    Lazy Loading not supported
    Missing LINQ Operators vs LINQ to SQL
    Generated SQL unreadable
    No support for Plain Old CLR Objects
    N-Tier difficult
  • 7. Entity Framework 4.0Removing the friction
    Better Tools and Design Experience
    More powerful/flexible runtime
    Persistence Ignorance*
    Code Only*
    * Delivered in .NET Framework 4 and a separate download
  • 8. Better Tools and Design Experience
    Model First
    Templated code generation
    Stored Procedures
    Complex Types
    Better delete and search
  • 9. Model First and Templated Code Generation
  • 10. More powerful/flexible runtime
    Lazy Loading (Deferred Loading in Beta 1 )
    Foreign Keys surfaced
    More complete LINQ implementation
    EntityFunctions and SqlFunctions
    Improvements to generated SQL
  • 11. Deferred Loading, Functions, Generated SQL
  • 12. http://blogs.msdn.com/adonet/archive/2009/08/05/improvements-to-the-generated-sql-in-net-4-0-beta1.aspx
  • 13. Persistence Ignorance
    First class support for Persistence Ignorance
    No modifications to your classes!
  • 14. Persistence Ignorance
  • 15. Code Only
    Create the database from the classes
    No model
    Convention to config
  • 16. Code Only
  • 17. N-Tier
    Self Tracking Entities
  • 18. N-Tier
  • 19. Entity Framework
    The designer!
    No support for Plain Old CLR Objects
    No Pluralization/Singularization
    Foreign Keys hidden
    Model First not supported
    Lazy Loading not supported
    Missing LINQ Operators vs LINQ to SQL
    Generated SQL unreadable
    N-Tier difficult
    Poor support for Stored Procedures
  • 20. Summary
    Entity Framework 4.0 is rather nice!
    We continue to listen and improve
    Install VS2010 Beta 2 http://bit.ly/vs2010b2
    My blog for EF 4 posts http://bit.ly/ericnelson
    Channel 9 Screencasts on EF4 http://bit.ly/ch9ukdevteam
    Entity Framework 4.0 Resources http://bit.ly/ef4resources
    Entity Framework Team Blog http://blogs.msdn.com/adonet/
    Entity Framework Design Blog http://blogs.msdn.com/efdesign/