Get started with Entity Framework 6
This guide contains a collection of links to selected documentation articles, walkthroughs and videos that can help you get started quickly:
Here you will learn how to add Entity Framework to your applications and, if you want to use the EF Designer, make sure you get it installed in Visual Studio.
Do you prefer to specify your EF model writing code or drawing boxes and lines? Are you going to use EF to map your objects to an existing database or would you like EF to create a database tailored for your objects? Here your learn about two different approaches to use EF6: EF Designer and Code First. Make sure you follow the discussion and watch the video about the different.
DbContext is the first and most important EF type that you need to learn how to use. It serves as the launchpad for database queries and keeps track of changes you make to objects so that they can be persisted back to the database.
Find out how to get help from the experts and contribute your own answers to the community.
Entity Framework 6 uses an open development model. Find out how you can help make EF even better by visiting our GitHub repository.
Index of Walkthroughs
- Code First to an Existing Database Workflow
- Code First to a New Database Workflow
- Mapping Enums Using Code First
- Mapping Spatial Types Using Code First
- Writing Custom Code First Conventions
- Using Code First Fluent Configuration with Visual Basic
- Code First Migrations
- Code First Migrations in Team Environments
- Automatic Code First Migrations (This is no longer recommended)
- Database First Workflow
- Model First Workflow
- Mapping Enums
- Mapping Spatial Types
- Table-Per Hierarchy Inheritance Mapping
- Table-Per Type Inheritance Mapping
- Stored Procedure Mapping for Updates
- Stored Procedure Mapping for Query
- Entity Splitting
- Table Splitting
- Defining Query (Advanced)
- Table-Valued Functions (Advanced)
- Async Query and Save
- Databinding with WinForms
- Databinding with WPF
- Disconnected scenarios with Self-Tracking Entities (This is no longer recommended)