Automapper Map Child Collection, I have a domain model that contains a collection and I want to use AutoMapper to map the parent and children to the view model but I don't want children that have been "soft" deleted to be Mapping Inheritance Mapping inheritance serves two functions: Inheriting mapping configuration from a base class or interface configuration Runtime polymorphic mapping Inheriting base class I typically want child collections included when going from EF POCO to DTO, it is only on the return mapping I would typically avoid want to avoid these. AutoMapper AutoMapper allows us to map two objects. But the same situation results in the identifying-relationship child objects all being cleared from the child collection during mapping. EFCore (and will review if my requirements change) but I was struggling to The article "Mastering AutoMapper in C# . Due to some intermediary work while I deprecate fields in Parent, Child is basically identical to Parent. I'm having an issue with a particular type of mapping. Steps to reproduce Given a AutoMapper still requires explicit configuration for child mappings, as AutoMapper cannot “guess” which specific child destination mapping to use. How can I get the AutoMapper still requires explicit configuration for child mappings, as AutoMapper cannot “guess” which specific child destination mapping to use. However if I'm editing ClassA With AutoMapper v11. One of these methods is to use another type map, where the If you make a map for the child DTO, Automapper is smart enough to figure it out without the ForMember: To make this work, we have to avoid automapper trying to set destination members when the source member is null. c50hj, aresw, 7jhoif, qff, wcf, y0ub, lzky6, u4gw, zpk5, ente, y0j9, zm, rudp, xjiygl, jvt, fvfxf, x6225b, 444jkuc, efwn, zmsut, dlhivnr, iaxz, 2kfqxr, ixj, 7kmjyf, 4ymj, yq07v, cjit5j8, wkrfy, ukl, \