从Entity Framework Database First迁移到Code First遇ObjectQuery及预加载问题

Let's break down what's going wrong and fix this step by step:

Why Your Current Code Fails #

1. Original Database First Approach: Casting the LINQ query to ObjectQuery<Post> with as returns null in Code First. EF4's Code First uses DbSet<T> which wraps the underlying query differently, so the as conversion doesn't work, leading to the "Object reference not set" error.
2. Modified Code Issue: Moving Include("Comments") to ctx.Posts.Include(...) gets rid of the null reference, but the from post in ... from blog in post.Blogs query structure breaks EF4's ability to track the eager load instruction. The Comments collection never gets preloaded, so when your ObjectContext is disposed, accessing Post.Comments throws the connection error.

Fix 1: Use Any() for Filtering (Recommended for Code First) #

Rewrite the filter using Any() to keep the query structure simple, which lets EF properly apply the Include directive:

var results = ctx.Posts
    .Include("Comments")
    .Where(post => post.Blogs.Any(blog => blog.Owner.EmailAddress == "alexj@microsoft.com"))
    .ToList();

• This approach is more idiomatic to Code First and avoids the query structure that breaks eager loading.
• Calling ToList() executes the query immediately, loading both Post and associated Comments into memory before the context is disposed.

Fix 2: Correctly Cast to ObjectQuery<Post> #

If you need to keep the original query structure, use explicit casting instead of as to ensure you get a valid ObjectQuery instance:

var results = ((ObjectQuery<Post>)(from post in ctx.Posts
                                   from blog in post.Blogs
                                   where blog.Owner.EmailAddress == "alexj@microsoft.com"
                                   select post))
              .Include("Comments")
              .ToList();

• The as operator returns null when the conversion isn't possible, but explicit casting throws a clear error if something's off (instead of a silent null reference).
• Again, always call ToList() (or another execution method like FirstOrDefault()) to load data before disposing the context.

Key Takeaway #

In EF4 Code First, eager loading with Include() works best when the query starts directly on the DbSet and uses simple filter expressions. Avoid complex query structures that disrupt EF's ability to track navigation properties for preloading.

内容的提问来源于stack exchange，提问作者crazyTech