Learn how Microsoft wanted EF Core to be a framework that handled concepts common to most datastores, with provider-specific extensions to become available when targeting a specific provider.
- [Instructor] According to Rowan Miller,…Microsoft's Entity Framework Program Manager,…Microsoft's vision for Entity Framework Core…was that they wanted it to be a core framework…that handles concepts common to most data stores…with provider specific extensions…to become available when you target a specific provider.…So in other words, Rowan not only wants it to be used…with relational data stores,…but also non-relational,…in addition to new devices like phones and tablets…that aren't dependent on the .NET framework.…
And along with being less dependent on the .NET framework,…Entity Framework Core will be delivered in small parts.…So while the previous version of Entity Framework…contained the entire Entity Framework platform,…Core will have the bare minimal.…It will be as lean as can be.…Smaller, composable NuGet packages…will provide whichever part…of the .NET API or Entity Framework that you need.…For example, if you're going to be doing NoSQL work,…in addition to the bare components of EF Core,…during the install you can include…
- Entity Framework (EF) overview
- Uses for EF
- Installing EF
- Creating entities
- Creating the DbContext
- Performing migrations
- Creating an MVC application
- Installing EF packages
- Reverse engineering the model
- Performing context and dependency injection
- Creating the controller and the view
- Using SqlServerTypeMapper
Skill Level Intermediate
Q: This course was updated on 06/23/2017. What changed?
A: The following topics were updated: using the exercise files; Mac install prerequisites; Entity Framework on Mac, part 1; and Entity Framework on Mac, part 2.