Entity Framework Core 5.0: The Next Generation for Data Access

Use C#, .NET classes, and LINQ to interact with databases like Sqlite, Azure SQL Server and even Azure Cosmos DB from .NET 5 apps with Entity Framework Core. See the latest features in action like many-to-many, table-per-type and filtered includes.

[MusicalGeniusBar]

Its insane how he explained ef core in 5 minutes

[Spivonious]

It took 13 years for EF to properly support many-to-many relationships.

[pascaldeclercq]

Nice demo!
Just tiny error I think: at 19:15 you are querying for the oldtimer members, but the query used actually looks for the newbies instead.

[leandrocasas]

This is one of my favorites from the whole event. Very information dense and very well explained!

[nove]

Very excited to try out these new EF Core features. Keep on with the updates!!

[javadborhani]

Shay Rojansky => this is the style I like someone to explain. thanks

[liammcmullen]

How nice to see things getting easier to do. Thanks!

[washington]

You explain things very well, Jeremy :)

[ARCHNOX]

Im happy to see the features of EF are now into EF Core 5. Its like a christmas day

[rey]

The new way of joining tables is just amazing. Thanks a lot for the improvement.

[lollo]

@19:51 - Line 30: I always liked the T-SQL BETWEEN-Statement. Is an Extension possible for "MemberSince" to be used inside the lambda-expression? like: m.MemberSince.Between(a, z)

[fullemptiness]

Typo at 2:12, POCO (Plain Old C#/CLR Object)
However I don't know why it is old 😅

[CodingHaribo]

As usual, another great release of EF-Core. Thank you and your team for the great work.
All these features are grealty welcomed by myself, especially of course, the many-to-many.
Also, fantastic succinct presentation, obviously well-planned.

[JustinMinnaar]

Excellent and clear talk, thank you. At 20:00, line 30, should not oldTimers be those before the date, not after?

[EricOuellet]

Great and clear explanations at a nice beat. BUT I have a lot of difficulty to be agree with you about using one table per hierarchy. It goes directly against "Normal form" (Boyce-Codd) and every advantages it has. Yes performance could be better in some case using one table oinly but it could also be less in some other cases. Plus, you have a lots of disadvantages of having unusefull fields in some cases and some other in other cases. You can loose a lot doing so in many ways (integrity, space, some performance on full table scan, etc). It could really become a huge mess.

[jeffbarnard]

Can you serialize these many:many relationships? How do you handle self referencing loops?

[rukascool]

Lovely features as always, thank you microsoft!
Hobby projects where perf doesn't matter, ToTable inheritence is really sweet.

[MusicalGeniusBar]

I would just like to point out how easy ef core is once you learn it, it makes a lot of sense

[markrobinson]

I've used every version of EF over the years and I've finally come to the conclusion that I simply don't need an ORM. I see no benefit.

I now prefer to use something like dapper to query the database and create simple objects. It's lightweight and very fast and I can write sql as my query. I find ORMs like EF to be so restrictive.

[masterdirin]

Came across a wierd phenomenon in EF Core 5.0 . . .

class A;
class B : A;
class C;

c = new C;
c.b = new B;

_context.Add(c);
_context.SaveChanges();

// after saving changes let's check what we have in c.b
// if B is configured as TPH then c.b is equal to b
// if B is configured as TPT then c.b is null, but b is OK