UseLazyLoadingProxies throws error because of some collections that cames from modules are not virtual #9605

12 Answer(s)

• 

  0

  AI-Bot created one month ago

  Support Team ABP Agent

  To use EF Core's UseLazyLoadingProxies in an ABP application, all navigation properties (including collections) in your entities must be marked as virtual. However, some ABP modules (such as GDPR) may define their entities without marking navigation properties as virtual. This causes the error you encountered:

  System.InvalidOperationException: Property 'GdprRequest.Infos' is not virtual. 'UseChangeTrackingProxies' requires all entity types to be public, unsealed, have virtual properties, and have a public or protected constructor. 'UseLazyLoadingProxies' requires only the navigation properties be virtual.
  

  Key Points

  • EF Core's lazy loading proxies require all navigation properties (including collections) to be virtual.
  • If a module's entity (like GdprRequest.Infos in the GDPR module) does not declare its navigation property as virtual, you cannot use UseLazyLoadingProxies unless you modify the source code of that module.
  • You cannot override or extend the navigation property to make it virtual from outside the module, due to C#'s type system and the way EF Core proxies work.

  Workarounds

  1. Do Not Use Lazy Loading Proxies:
     If you depend on ABP modules that do not mark navigation properties as virtual, you cannot use EF Core's lazy loading proxies unless those modules are updated. Instead, use explicit or eager loading (Include, ThenInclude, or ABP's WithDetails).

  2. Request Module Update:
     You can request the maintainers of the ABP modules (such as GDPR) to update their entities to make navigation properties virtual. This is the only way to enable lazy loading proxies for those entities.

  3. Fork and Patch (Not Recommended for Commercial Modules):
     If you have access to the module's source code, you could fork and update the navigation properties to be virtual. However, this is not recommended for commercial modules or if you want to keep receiving updates.

  Example: Eager Loading Instead

  Instead of relying on lazy loading, use eager loading:

  var gdprRequest = await _gdprRequestRepository
      .WithDetails(x => x.Infos)
      .FirstOrDefaultAsync(x => x.Id == id);
  

  Or with EF Core's Include:

  var gdprRequest = await dbContext.GdprRequests
      .Include(x => x.Infos)
      .FirstOrDefaultAsync(x => x.Id == id);
  

  Summary

  You cannot use UseLazyLoadingProxies with ABP modules that do not declare navigation properties as virtual. Use eager or explicit loading as an alternative, or request the module authors to update their code.

  Sources:

  • ABP EF Core Lazy Loading with Proxies

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Save Cancel
• 

  0

  cetin.sahin created one month ago

  Ai says : Request Module Update: You can request the maintainers of the ABP modules (such as GDPR) to update their entities to make navigation properties virtual. This is the only way to enable lazy loading proxies for those entities. so i am requesting update. Thanks

  Save Cancel
• 

  0

  maliming created one month ago

  Support Team Fullstack Developer

  hi

  What is your abp version?

  I will make all properties virtual in the next patch version.

  Thanks.

  Save Cancel
• 

  0

  cetin.sahin created one month ago

  our abp version is 9.1.0. but we upgrading to last version these days

  Save Cancel
• 

  0

  maliming created one month ago

  Support Team Fullstack Developer

  Thanks, I will change it in next 9.2 patch version

  Save Cancel
• 

  0

  cetin.sahin created one month ago

  thank you

  Save Cancel
• 

  0

  maliming created one month ago

  Support Team Fullstack Developer

  : )

  Save Cancel
• 

  0

  cetin.sahin created one month ago

  can you refund aur ticket?

  Save Cancel
• 

  0

  maliming created one month ago

  Support Team Fullstack Developer

  Of course.

  Save Cancel
• 

  0

  maliming created one month ago

  Support Team Fullstack Developer

  

  Save Cancel
• 

  0

  cetin.sahin created one month ago

  Which version will this change come in? is 9.2.2 version include this development ?

  Save Cancel
• 

  0

  maliming created one month ago

  Support Team Fullstack Developer

  hi

  9.2.3

  Save Cancel