Please consider this one. It would make it much easier to work with table per type when you need to know the object type but not retrieve it's properties.
This feature has been implemented in EF Core and is coming in 2.1.
Issue tracking this feature: https://github.com/aspnet/EntityFramework/issues/3910.
398 votes13 comments · [Closed] WCF Data Services Feature Suggestions · Flag idea as inappropriate… · Admin →
Can't agree more.
Being unable to update EF is already a burden, I can't imagine the problems later on when more features are added and bugs are fixed on EF and we just can't update it because WCF Data is stuck.
We stumbled upon this problem just a few hours ago. We were trying to map an inheritance chain using TPT against a base interface and discovered that EF does not support mapping to interfaces at all.
We had to go from an IEvent interface to a EventBase abstract class for it to work, but this pollutes the whole solution and is seemingly the exact same thing for EF.
I wonder what exactly complicates things here. Isn't it trivial to implement this in the next version of EF Code First?