@sgifford Thanks for reporting this! I have created the following work item for it: https://entityframework.codeplex.com/workitem/1566
The workaround is to set the navigation property in the entity constructor so that EF will not attempt to create an instance of the custom collection class. For example:
The workaround is to set the navigation property in the entity constructor so that EF will not attempt to create an instance of the custom collection class. For example:
class MyMasterObject
{
public MyMasterObject
{
Details = new MyCollection();
}
public virtual MyCollection Details { get; set; }
}