Dump() of EFCore 3.1 entities with lazy-loading traces entire graph

Similar to this issue from 7 years ago, but this only affects Dump()-ing for us.

Taking Joe's guidance from that issue, when the output is dumped to grids the issue goes away.

We're on net472. The DbContextOptions is created with UseLazyLoadingProxies.

We're migrating from EF5 with the Legacy context in which this problem was not present. Notably, the output of the original Dump() would not include any navigation properties unless they were previously fetched while Dump()-ing the EFCore 3.1 entities picks up every navigation property.

I'm using LINQPad 5 (AnyCPU).

Anyone have similar issues and/or know a mitigation?


Sign In or Register to comment.