) is the only upgrade guide I found on the wiki, and I followed it in every applicable instance with out Converters and Value Resolvers. In the cases where we have specific circular references that need to be retained, I included the .PreserveReferences() to those mappings.
When I continued to get stack overflow exceptions, I considered that maybe Automapper thought of mapping an object with a Lis<[ComplexObjectNameHere]>t to ICollection<[ComplexObjectNameHere]> (and vice versa) was some sort of circular reference, and tried applying PreserveReferences() to those maps as well, but with no improvement. Then I tried MaxDepth() with depth values ranging from 1-10, also with no improvement.
Nothing else in the guide I linked makes specific reference to problems with mapping objects with members that are Collections of complex objects, but maybe I followed the wrong guide? Or I just don't understand how a different section of the guide applies to my current issue? I have searched for awhile now and created a bunch of test cases and havn't been able to determine any other possible cause for the Stack overflow exceptions, nor determined any solutions that doesn't involve taking each List of objects in a mapped object and mapping each value individually in a loop and adding the result to the Destination object's List member...which frankly is not a viable solution for us as a result of an upgrade.
If I'm doing something wrong, or missing something in the guide, please let me know.