Entity Framework Code First Lazy Loading

44,687

Solution 1

This is wrong

"virtual" keyword is used for not loading the entities unless you explicit this (using an "Include" statement)

Lazy Loading means that entities will be automatically loaded when you first access collection or navigation property, and that will happen transparently, as though they were always loaded with parent object.

Using "include" is loading on demand, when you specify properties you want to query.

Existence of virtual keyword is related only to lazy loading. virtual keyword allows entity framework runtime create dynamic proxies for your entity classes and their properties, and by that support lazy loading. Without virtual, lazy loading will not be supported, and you get null on collection properties.

Fact is that you can use "include" in any case, but without lazy loading it is the only way to access collection and navigation properties.

Solution 2

I guess you're quiring for a property which is a subject for lazy load while being into the ef context:

using (var db = new Context())
{
    var user = db.Users.Where(...);

    var products = user.Products; // being loaded right away
}

Try to leave it:

User user;
using (var db = new Context())
{
    user = db.Users.Where(...);

    // I guess you will need here:
    // .Include(u => u.Products)
}
var products = user.Products; // what error will you get here?
Share:
44,687
Catalin
Author by

Catalin

Hello, My name is Catalin and I am a full-stack developer with the primary focus on .NET. Some of the technologies I like to work with include: ASP.NET Core, AWS, Azure, MongoDB, JavaScript, RequireJS, Gulp, React, RabbitMQ, AWS SAM I like challenges, I am a strong advocate of constant refactoring and I try to avoid coding compromises as much as possible. On my spare time I like to work on my personal project, https://github.com/KissLog-net/KissLog.Sdk Some of my favorite (professional) books are: Adaptive Code via C#: Agile coding with design patterns and SOLID principles Learning JavaScript Design Patterns Pragmatic Programmer

Updated on July 14, 2020

Comments

  • Catalin
    Catalin almost 4 years

    I am having two object classes

    public class User
    {
        public Guid Id { get; set; }
        public string Name { get; set; }
    
        // Navigation
        public ICollection<Product> Products { get; set; }
    }
    
    public class Product
    {
        public Guid Id { get; set; }
    
        // Navigation
        public User User { get; set; }
        public Guid User_Id { get; set; }
    
        public string Name { get; set; }
    }
    

    When i load a user using dataContext, i get the list of Products being null (this is ok).

    If i add "virtual" keyword to Products list,

    public virtual ICollection<Product> Products { get; set; }
    

    when i load the user, i get the Products list as well.

    Why is this happening? I thought that "virtual" keyword is used for not loading the entities unless you explicit this (using an "Include" statement)

    I think i got it all wrong