This document discusses the evolution of Entity Framework 4.0 and its future. It begins with an introduction and agenda. Then it outlines many of the new features included in Entity Framework 4.0 like model-first development, foreign keys, POCO support, lazy loading, and more. It describes three possible routes for development: starting with the database, an EDMX model, or .NET classes. It concludes with a brief section on the future.

1. Evolução da Entity Framework 4.0 e o seu futuro DEV415 NunoGodinho Partner & CTO @ ITech4All nuno.godinho@itech4all.com @NunoGodinho

2. Session abstract Session title

3. Speaker Bio and Photo Speaker Name

4. Nuno Filipe Godinho Partner & CTO @ ITech4all Mail: Nuno.Godinho@itech4all.com Nuno.Godinho@sapo.pt Blogs: http://pontonetpt.com/blogs/nunogodinho http://xamlpt.com/blogs/nunogodinho http://weblogs.asp.net/nunogodinho http://msmvps.org/blogs/nunogodinho Twitter: @NunoGodinho About Me

5. Introduction New Features Possible Routes Future Q&A Agenda

6. Introduction

7. Visual Studio “Quadrant” Entity Framework Data Services ADO.NET “M”/EDM SQL Server SQL Azure … SQL Server Modeling Services

8. New Features

9. How many new features can we demo in one session?

10. Model-first development Automatic pluralization Foreign keys in models POCO class support Lazy loading T4 Code Generation Template customization IObjectSet Virtual SaveChanges ObjectStateManagercontrol New in Entity Framework 4.0 Self-tracking entities SQL generation improvements More LINQ operator support LINQ extensibility ExecuteStoreQuery ExecuteStoreCommand SPROC import improvements Model defined functions WPF designer integration Code-Only development (Feature CTP)

11. New Features

12. start with the database “database is the truth” why? it already exists, or you want low level control over the database what? import model into edmx and tweak start with an edmx model “edmx is the truth” why? you want separation from code and database in a declarative format what? create a model and tweak start with .net classes “code is the truth” why? primarily focused on code shape, database is an implementation detail what? define classes in code, adjust shape using contextbuilder Possible Routes

13. Futures