.Query <T> for T with nested objects
Possible duplicate:
How to efficiently select an aggregate object using Dapper?
Is it possible to force dapper to create instances of nested objects, and if so, are there any examples of this in action?
In most cases .net primitives are enough for me, but not always. A hack may be to include a foreign key as primitives in the parent type, and then subsequently create based on this. I hope this is not necessary, as this will create unwanted noise in the POCO model.
+6
No one has answered this question yet.
See similar questions:
or similar: