EntityException thrown executing EF6 query with .Includes()

Question

I am having trouble migrating an EF4 solution to EF6.

We use T4 templates to generate persistent ignorant POCOs that have navigation properties based on ObservableCollection< T>.

Because our ObjectContext implementation exposes entity sets as IObjectSet< entity> we lose the Include() method from ObjectQuery and so have to use an extension method on IQueryable to regain it, as follows:

public static IQueryable<TSource> Include<TSource>(this IQueryable<TSource> source, string path)
{
    IQueryable<TSource> returnValue = source;
    var objectQuery = source as ObjectQuery<TSource>;

    if (objectQuery != null)
    {
        returnValue = objectQuery.Include(path);
    }

    return returnValue;
}

Having updated the solution to use EF6 we now see the following System.Data.Entity.Core.EntityException when executing queries using .Include() :-

"The navigation property 'Details' on entity of type 'DataEntities.Parent' must implement ICollection< T> in order for Entity Framework to be able to track changes in collections."

What I don't get is the 'Details' property is a custom type that inherits ObservableCollection< T> which is an ICollection< T>, so why the exception that states it must implement ICollection< T>?

If anyone has any light to shed on this I would be grateful, thanks.

Amazing how the answer often presents itself just as you ask the question! Basically, our navigation properties were defined as ObservableCollection. It would appear that defining the collection type as an Interface is no longer supported. Changing them to ObservableCollection is all that is required. — user2932125, Oct 29 '13 at 14:36
A different problem, but this link - [link](http://stackoverflow.com/questions/8747442/error-when-using-interfaces-for-entity-framework-4-2-entities) - provided the missing piece of the puzzle. — user2932125, Oct 29 '13 at 14:40

score 0 · Answer 1 · edited May 23 '17 at 12:05

0

As explained in this blogpost of an EF team member

The rules that your classes must follow to enable change-tracking proxies are quite strict and restrictive. This limits how you can define your entities and prevents the use of things like private properties or even private setters.

The rules are:

The class must be public and not sealed.
All properties must have public/protected virtual getters and setters.
Collection navigation properties must be declared as ICollection. They cannot be IList, List, HashSet, and so on.

And this answer for an explanation why you can't use your implementation.

edited May 23 '17 at 12:05

Community

1
1

answered Oct 29 '13 at 14:10

Loetn

3,832
25
41

Thank you for taking the time to answer my post. We are using snapshot change-tracking, not change-tracking proxies, which only added to the confusion raised by the exception. Having discovered that we can no longer define navigation properties as a collection of type IEntity and must instead define them as a collection of type Entity our implementation is back in business. – user2932125 Oct 29 '13 at 15:31

EntityException thrown executing EF6 query with .Includes()

1 Answers1