670 votes14 comments · Entity Framework Feature Suggestions » runtime · Flag idea as inappropriate… · Admin →
This feature is currently planned to be included in EF7.
Daniel Simmons has an explanation here
(see scenario #1).
I do not see how the current implementation is actually better than deleting the orphaned objects though.
And Thank You Richard for an awesome workaround! Love it.
274 votes11 comments · Entity Framework Feature Suggestions » runtime · Flag idea as inappropriate… · Admin →
Reverting status from “under review” to “no status” since we aren’t currently working on this. We will still consider it for future releases.
I hope this does not require me to have a DTO for each object in the Domain Model, though. I would like to store Domain Model objects directly with no DTO and be able to specify an IoC container to create entities.
UPDATE: EF7 opens up to external IoC containers through integration with ASP.NET vNext Dependency Injection abstractions.
EF6 alpha 1 includes a service locator-based system for plugging in alternate implementations of specific services. See here for a spec: http://entityframework.codeplex.com/wikipage?title=EF%20Configuration%20and%20Extensibility
However, materialization is still not extensible in or other mechanism.