Skip to main content

EF Core - Lazy loading without a proxy

Yesterday I talked about lazy loading and how you can avoid the usage of proxy objects in NHibernate. Writing that post made me wonder if a similar thing is possible in Entity Framework Core. Let's find out!

Remark: If you want to learn more about the concept of lazy loading check out my previous post first.

Lazy loading in Entity Framework

Lazy loading in Entity Framework works quite similar to NHibernate and also uses a proxy object by default. Therefore you need to install the Microsoft.EntityFrameworkCore.Proxies package and enabling it with a call to UseLazyLoadingProxies.

.AddDbContext<BookContext>(
b => b.UseLazyLoadingProxies()
.UseSqlServer(myConnectionString));
view raw AddDbContext.cs hosted with ā¤ by GitHub

Contrary to NHibernate you don’t need to make all your properties virtual but only those where lazy loading should be enabled:

public class Author
{
public int Id { get; set; }
public string Name { get; set; }
public DateTime BirthDate { get; set; }
public virtual ICollection<Book> Books { get; set; }
}
view raw Author.cs hosted with ā¤ by GitHub
public class Book
{
public int Id { get; set; }
public string Title { get; set; }
public int Year { get; set; }
public virtual Author Author { get; set; }
}
view raw Book.cs hosted with ā¤ by GitHub

Lazy loading without a proxy

Lazy loading without a proxy object in Entity Framework IS possible although it requires a bit more work than when using NHibernate.

For Entity Framework you need to explicitly inject the ILazyLoader service and than use this service to fetch the related data:

public class Author
{
private ICollection<Book> _books;
private ILazyLoader LazyLoader { get; set; }
public Author()
{
}
private Author(ILazyLoader lazyLoader)
{
LazyLoader = lazyLoader;
}
public int Id { get; set; }
public string Name { get; set; }
public ICollection<Book> Books
{
get => LazyLoader.Load(this, ref _books);
set => _books = value;
}
}
view raw Author.cs hosted with ā¤ by GitHub
public class Book
{
private Author _author;
public Book()
{
}
private Book(ILazyLoader lazyLoader)
{
LazyLoader = lazyLoader;
}
private ILazyLoader LazyLoader { get; set; }
public int Id { get; set; }
public string Title { get; set; }
public int Year { get; set; }
public Author Author
{
get => LazyLoader.Load(this, ref _author);
set => _author = value;
}
}
view raw Book.cs hosted with ā¤ by GitHub

More information: Lazy Loading of Related Data - EF Core | Microsoft Learn

Popular posts from this blog

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

.NET 9 - Goodbye sln!

Although the csproj file evolved and simplified a lot over time, the Visual Studio solution file (.sln) remained an ugly file format full of magic GUIDs. With the latest .NET 9 SDK(9.0.200), we finally got an alternative; a new XML-based solution file(.slnx) got introduced in preview. So say goodbye to this ugly sln file: And meet his better looking slnx brother instead: To use this feature we first have to enable it: Go to Tools -> Options -> Environment -> Preview Features Check the checkbox next to Use Solution File Persistence Model Now we can migrate an existing sln file to slnx using the following command: dotnet sln migrate AICalculator.sln .slnx file D:\Projects\Test\AICalculator\AICalculator.slnx generated. Or create a new Visual Studio solution using the slnx format: dotnet new sln --format slnx The template "Solution File" was created successfully. The new format is not yet recognized by VSCode but it does work in Jetbr...