New Post: NotMapped Attribute in EF 5

I have a situation where our team is attempting to generate our DBContext class. The problem we've run into is that we are unable to guarantee our base types are discovered before our derived types. It looks like through the principle of reachability EF is discovering derived types regardless of the order we place DBSet properties or calls to modelBuilder.Entity<>.

Any advice on how we might do one of the following:

1. Turn off automatic type discovery
2. Through some use of DBSet property order of ModelBuilder.Entity<> call order; guarantee base types are always discovered before derived types,
   

Thanks for taking the time to read this post.

Duane