When I use Entity Framework, relationships between tables are defined through navigation properties which are references between classes. Such properties normally defined as virtual like this:
public virtual Request Request { get; set; }
Dapper.Contrib fails on any of such properties. I should mark all of them like [Write(false)] then it works.
I simply can't believe that I should do this manually over all my POCOs! Virtual properties are commonly recognizable as exception from mapping in many libraries.
When I use Entity Framework, relationships between tables are defined through navigation properties which are references between classes. Such properties normally defined as virtual like this:
public virtual Request Request { get; set; }
Dapper.Contrib fails on any of such properties. I should mark all of them like [Write(false)] then it works. I simply can't believe that I should do this manually over all my POCOs! Virtual properties are commonly recognizable as exception from mapping in many libraries.
Am I missing something?