So this is part of the reason that reverse mapping is taking a while to put in. It's those "when appropriate" decisions that vary wildly from user to user and scenario to scenario. I've had requests like:
- Always clear collections
- Never clear collections, only add
- Never instantiate new objects if the object already exists
- Always instantiate new objects, no matter what
- Collections are encapsulated (i.e., the List<T> is not public), so you need to find the AddFoo method for the corresponding GetFoos() one
- Only instantiate objects if it's of a certain base type (Entity), but ALWAYS overwrite other kinds of objects
- Only set some of the members you find from the original destination type
etc
I do like to see these examples, as our systems don't have the need for reverse mapping. We're getting to the point where we don't expose setters on our domain objects. Any new insight in to what folks need would be fantastic.
Thanks,