navigation property should be virtual – not required in ef core?

by

virtual was never required in EF. It was needed only if you want lazy loading support.

Since Lazy loading is not yet supported by EF Core, currently virtual have no special meaning. It would when (and if) they add lazy loading support (there is a plan for doing so).

Update: Starting with EF Core 2.1, Lazy loading is now supported. But if you don’t add Microsoft.EntityFrameworkCore.Proxies package and enable it via UseLazyLoadingProxies, the original answer still applies.

However if you do so, the thing’s totally changed due to the lack of the opt-in control in the initial implementation – it requires all your navigation properties to be virtual. Which makes no sense to me, you’d better not use that until it gets fixed. If you really need lazy loading, use the alternative Lazy loading without proxies approach, in which case again virtual doesn’t matter.

More Related Contents:

  1. EF codefirst : Should I initialize navigation properties?
  2. Entering keys manually with Entity Framework
  3. Many-to-many self referencing relationship
  4. Can I reuse code for selecting a custom DTO object for a child property with EF Core?
  5. Filter all queries (trying to achieve soft delete)
  6. How to add the same column to all entities in EF Core?
  7. Entity Framework – Add Navigation Property Manually
  8. Dynamically changing schema in Entity Framework Core
  9. Include with FromSqlRaw and stored procedure in EF Core 3.1
  10. Could not load file or assembly Microsoft.Extensions.DependencyInjection.Abstractions, Version=1.1.0.0
  11. Entity framework EF.Functions.Like vs string.Contains
  12. The LINQ expression could not be translated and will be evaluated locally
  13. Entity Framework | Sequence contains more than one matching element
  14. Unable to edit db entries using EFCore, EntityState.Modified: “Database operation expected to affect 1 row(s) but actually affected 0 row(s).”
  15. Working with SQL views in Entity Framework Core
  16. EF models. Navigation properties can only participate in a single relationship
  17. Implementing recursive property loading in EF Core
  18. How to set Identity Seed value in code-first?
  19. Entity Framework change connection at runtime
  20. Entity Framework Refresh context? [closed]
  21. EntityType has no key defined error
  22. How to mock an async repository with Entity Framework Core
  23. Linq to EntityFramework DateTime
  24. Mapping Database Views to EF 5.0 Code First w/Migrations
  25. DbSet.Attach(entity) vs DbContext.Entry(entity).State = EntityState.Modified
  26. Entity Framework Core Using multiple DbContexts
  27. Autonumber with Entity Framework
  28. Unable to find the requested .Net Framework Data Provider. It may not be installed
  29. How can set a default value constraint with Entity Framework 6 Code First?
  30. Why Entity Framework performs faster than Dapper in direct select statement [closed]

Leave a Comment