Entity Framework Core

Download this episode

Download Video

Download captions

Download Captions

Description

In this episode, Robert is joined by Julie Lerman, who takes us on a deep-dive tour of many of the features that are new in Entity Framework Core.

Julie covers:

  • Overview of Entity Framework Core [00:35]
  • Migrating an existing .NET Core project that uses project.json to use the new MSBuild based tooling [04:12]
  • Field mappings and encapsulated collections [23:20]
  • Turning change tracking off for a DBContext [36:45]
  • In-Memory provider for unit testing [44:55]
  • Using the .NET Core CLI for migrations [1:08:40]
 

Embed

Format

Available formats for this video:

Actual format may change based on video formats available and browser capability.

    The Discussion

    • User profile image
      dubem

      Pretty cool session. Learnt something new (a)

    • User profile image
      robcube

      do you know when it'll be subtitled or provide a transcript?

    • User profile image
      julielerman

      I've added some quick EF Core walk though videos on Channel 9 that you can follow along with if you like. You can find them on my "niners" page at channel9.msdn.com/Niners/julielerman

    • User profile image
      ltuttini

      hi

      I can see the CC and translation to several idioms, but why isn't Spanish ?
      the same happen with the other videos

      regards

    • User profile image
      velchev

      Very cool. I am especially interested in the improvements they are doing in EF core with the mapping to a private fields. 

      What normally should happen with EF mapped entity classes is that they are mapped to Domain Classes which contain the Domain knowledge about the specific thing. I think that should still remain as we do not want modifying directly EF class but Business Domain class, and then after that mapping to Entity. But with the new idea of having private field - this will allow to hide some internal knowledge of the Entity to its implementation. That could be good but also bad thing. Bad because allows Business Logic to be in the Domain but also in the Entities. Wondering if EF team want to remove the gap between those two things and Entity class to have the most intimate knowledge about the domain.... ? What do you think?

    • User profile image
      julielerman

      @ltuttini:I brought this up with some channel 9 people. I don't think they realized this and they are looking into it now! thanks for pointing it out!!:)

    Add Your 2 Cents