Use case ForAllOtherMembers?

Consider two types with a large number of properties that will auto-map due to common names between them, say there are 30 such properties. However, you only want 10 of these to auto-map and the remaining 20 to be ignored and not mapped. Further, imagine that the remainder are to be auto-mapped from another type whose properties also line up; so, for that map, it is desired that the 20 will auto-map there, and the 10 here ignored there.

The accepted answer in discussion 4036 seems to say you should “manually / explicitly” map the 10 properties (to use @jbogard 's language from the discussion) in the first map, and the 20 in the second, even though all 30 satisfy the auto-mapping convention, in that source and destination property names are identical.

Since these subsets of properties fit the use-case for auto-mapping, there should be a way to tell AutoMapper to auto-map just the subset of properties but ignore the rest.

Suppose there was an overload of ForMember() that only took one argument, a selector for the properties to auto-map. Something like, .ForMember(x=>new[]{x.Prop1, x.Prop2, ..., x.PropN}) , where you list the properties you want auto-mapped from the source, but you didn’t have to explicitly give the source properties in a MapFrom argument for each, since they all had the same names anyway, so should not have to be explicitly listed (back to manual mapping).

With a solution like this one, Ignore with ForAllOtherMembers seems to now have a use case, since for the 10-map, you need to ignore the remaining 20, and for the 20-map, you need to ignore the 10.