This document discusses Entity Framework Core 1, which is a new version of Entity Framework designed for .NET Core. It highlights some key changes and new features in Entity Framework Core 1 compared to the previous EF 6 version. These include a focus on Code First development, removal of the ObjectContext API, and support for additional database providers and platforms like NoSQL, Linux, and Universal Windows Apps. While EF Core 1 brings new capabilities, the document recommends continuing to use EF 6 for most applications for now due to some limitations in the initial EF Core 1 release.

1. 1
Entity Framework Core 1 (formerly EF 7):
New features and changes
Manfred Steyer
About me …
Manfred Steyer
Trainer & Consultant
Angular & .NET
Page  2

2. 2
Contents
Entity Framework Today
Current Influences
Entity Framework Tomorrow
DEMO
Conclusion
Folie 4
ENTITY FRAMEWORK TODAY
Page  5

3. 3
EF 6.x
Folie 7
O/R-Mapper
Mature
(since 2008)
Optimized
Ecosystem
Integration
Recommended LINQ
Modes of Operation
Folie 8
• Model First
• DB First
Mapping via XML
• Code First
• Code First with Reverse Engineering
Mapping via Code

4. 4
Code First brings several advantages
Folie 9
Reverse
Engineering
Source Control
More Intuitive for
Developers
More Freedom
for Developers
Code-based
Configuration
Conventions
Migrations
DbContext
Object Model
Folie 10
ObjectContext

5. 5
CURRENT INFLUENCES
Page  11
Folie 12

6. 6
Folie 13
ENTITY FRAMEWORK
TOMORROW
Page  14

7. 7
Goals
Reach
• .NET Core
• NoSQL
Tity up
• Focus: Code First
• RIP ObjectContext
Folie 15
Non-Goals
Folie 16
• Yes, but only when it
really makes sense
API-
Changes
• NoSQL != RDBMS
Abstract
Paradigms

8. 8
Migration
You have to modify existing code
 Don't do it now!
Current Version 6.x will stay
Feature Set now
Folie 18
EF 6
EF Core 1
EF 6 is still the recommended version!

9. 9
Feature Set in Future
Folie 19
EF 6
EF Core 1.x+
Some Limitations in EF Core 1.x
 M:N-Relations
 Model it with two 1:N
 Lazy Loading
 Just TPH-Inheritance
 Complex Types
 Custom Conventions
 Mappings to Stored Procedures
 Update Model from Database
 Non-relational Providers

10. 10
Some new Features
Handling of detached Entities
Improvements for Eager-Loading and Batching
Client-Evaluation and Raw SQL
Shadow State
Alternate Keys
Linux, Universal-Apps
PostgreSQL, SQLite
Folie 21
Core 1.x or 6.x
Web with
.NET Core
EF Core
1.0
Universal
Apps
EF Core
1.0
Else EF 6.x
Code Frist

11. 11
DEMO
Page  23
Conclusion
 EF Core 1.x: Spring-Cleaning
 Getting rid of Legacy
 One Mode of Operation: "Code First"
 Time seems to be fitting: .NET Core
 Increasing Reach:
NoSQL, Linux, Universal-Apps (.NET Core)
 Providers for SQL Server, PostgreSQL, SQLite
 New features, like Batching or Shadow Properties
 EF 6.x is still recommended
Folie 24

12. 12
manfred.steyer@SOFTWAREarchitekt.at
SOFTWAREarchitekt.at
ManfredSteyer
Contact