Lazy Loading after mapping

I use Entity Framework and I want to map navigation properties to my DTO’s. So, my question is EF’s navigation properties by default have Lazy loading, its possible with auto mapper after mapping to have the same functionality of lazy loading to my DTO’s.

Here is my DTO’s :

    public class CustomerDTO
    {
        public string CustomerID { get; set; }
        public string CompanyName { get; set; }
        public ICollection<Order> Orders { get; set; }
     }

    public class OrderDTO
    {
        public int OrderID { get; set; }
        public string CustomerID { get; set; }
        public int? EmployeeID { get; set; }
        public string ShipName { get; set; }
        public string ShipAddress { get; set; }
        public Employee Employee { get; set; }
        public Customer Customer { get; set; }
        public  ICollection<OrderDetail> OrderDetails { get; set; }
    }

    public class OrderDetailDTO
    {
        public int OrderID { get; set; }
        public decimal UnitPrice { get; set; }
        public short Quantity { get; set; }
        public Order Order { get; set; }
    }
    
     public class EmployeeDTO
    {
        public int EmployeeID { get; set; }
        public string LastName { get; set; }
        public string FirstName { get; set; }
        public ICollection<Order> Orders { get; set; }
    }

Persistent Models:

    public class Customer
    {
        public string CustomerID { get; set; }
        public string CompanyName { get; set; }
        public ICollection<Order> Orders { get; set; }
     }

    public class Order
    {
        public int OrderID { get; set; }
        public string CustomerID { get; set; }
        public int? EmployeeID { get; set; }
        public string ShipName { get; set; }
        public string ShipAddress { get; set; }
        public Employee Employee { get; set; }
        public Customer Customer { get; set; }
        public  ICollection<OrderDetail> OrderDetails { get; set; }
    }

    public class OrderDetail
    {
        public int OrderID { get; set; }
        public decimal UnitPrice { get; set; }
        public short Quantity { get; set; }
        public Order Order { get; set; }
    }
    
     public class Employee
    {
        public int EmployeeID { get; set; }
        public string LastName { get; set; }
        public string FirstName { get; set; }
        public ICollection<Order> Orders { get; set; }
    }

[jbogard]

I’ve changed ORMs several times on various projects, and I promise you, layering and indirection makes it MUCH harder to do so, even impossible.

On Thu, May 18, 2017 at 5:46 AM Efstathios Chrysikos < [e-mail]> wrote:

My intention is to separate completely the ORM Layer from my model. One reason to do this is because maybe in the future the Project Leader will decide to change the ORM. So, to achieve this, I don’t want my repositories to return or take Persistent Model directly but Domain Model which will mapped to PM and after submitted for the specific job to the ORM?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/AutoMapper/AutoMapper/issues/2113#issuecomment-302355815, or mute the thread https://github.com/notifications/unsubscribe-auth/AAGYMkYOMuyBc64TQ2sfSWjr3gcKwgZZks5r7BN4gaJpZM4Ne8-0 .

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.