EF Core 3: Configure backing field of navigation property

c# domain-driven-design ef-core-3.1 entity-framework-core


Consider the following class. It tries to protect the access to the _assignedTrays.

Actually, it works perfectly, since EF automatically links the backing field _assignedTrays to the property AssignedTrays - by convention (msdn)

    public class Rack
        private List<Tray> _assignedTrays = new List<Tray>();

        private Rack()

        public Rack(string rackId)
            this.Id = rackId;

        public string Id { get; private set; }

        public IReadOnlyList<Tray> AssignedTrays => this._assignedTrays.AsReadOnly();

        public void Assign(params Tray[] trays)

The problem is, that our coding styles forbid the use of underscores in variable names ;-)

According to other code examples (here) it should be possible to just rename _assignedTrays to assignedTrays and just explicitly inform EF about that change in the OnModelCreating:

    modelBuilder.Entity<Rack>(e =>
        e.Property(t => t.AssignedTrays).HasField("assignedTrays");

But that gives me the following exception:

System.InvalidOperationException: The property 'Rack.AssignedTrays' is of type 'IReadOnlyList<Tray>' which 
is not supported by current database provider. Either change the property CLR type or ignore the property
using the '[NotMapped]' attribute or by using 'EntityTypeBuilder.Ignore' in 'OnModelCreating'.

What am I missing here? Shouldn't it work?

3/10/2020 6:35:13 PM

Accepted Answer

The documentation does not reflect the actual rules, because <camel-cased property name> (the "standard" C# backing field naming convention) is definitely supported, and probably even with highest priority.

But let say your naming convention is not supported. You can still map the backing field, but you can't do that with Property fluent API, because by EF Core terminology navigation properties are not "properties", but "navigations". This applies to all fluent, change tracking etc. APIs.

In order to configure navigation, you need to get access to the relationship builder. Then you can use the PrincipalToDependent and DependentToPrrncipal properties of the associated metadata to access/configure the two ends of the relationship.

Or use directly the metadata APIs (currently there is no dedicated fluent API for that anyway).

For instance:

3/10/2020 1:36:32 PM

Related Questions


Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow
Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow