Today we are excited to announce the release of Entity Framework (EF)
Core 2.1. This is the latest production-ready release of our open-source
and cross-platform data access technology.
.NET Core 2.1.0 (along with ASP.NET Core and Entity Framework Core)
will be released around May 30th, but for folks who can't wait until
then and would like to get their hands on the bits a little early, read
on!
Rider 2018.1 adds support for Roslyn analyzers and Entity Framework, introduces XAML preview, takes Unity integration to a whole new level, improves debugger with Memory view and other updates, evolves F# and NuGet support.
If you decide on using an Enum with enumerated values in your Entity Framework class, here are the tools you'll need to make it work. But an enumerated value shouldn't be your first choice.
In Entity Framework 4.1+ we would validate entities before sending them to the database. We don’t perform validation in EF Core, but there is a quick way to add at least some of it back.
I'm getting lots of request from the readers of my blog about writing a post on how to use stored procedure with Entity Framework Code First. So, in this post we're going to do just that.
In this short video Rowan describes shadow properties new in Entity
Framework 7. This is a super useful feature for those times when your
database and your class model don't quite match up.
In this short video Rowan takes us through a different approach to generating keys in Entity Framework 7 using sequences. This approach is interesting in cases of large INSERT batches primarily because keys are all fetched beforehand.
Entity Framework supports three ways to load related data - eager
loading, lazy loading and explicit loading. The techniques shown in this
topic apply equally to models created with Code First and the EF
Designer.