Entity Framework Code First Lazy Loading
c#, ef-code-first, entity-framework, entity-framework-4, lazy-loading
Solution
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.
Problem
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