This feature is at least partially implemented in EF Core 2.1. There is no custom binding but many additional patterns are now supported by convention, including injecting the property values in the constructor, injecting instances of services also in the constructor and on properties.
Direct mapping to fields was already supported in 1.1.Rachael Ross commented
As a way to enforce model rules, devs don't want to have a publicly accessible default constructor at times. Please support this so we can maintain the purity of our design decisions.
322 votesRachael Ross commented
PLEASE SUPPORT!!!!!!! Being new to EF, after I created my entire code first model with interfaces included, I was absolutely shocked that EF didn't offer support for this. Very close to moving to NHibernate at this point just to keep my domain model pure.