Unexpected AutoMapper behavior
With every upgrade of a major version of AutoMapper
there are many things that break. Recently I've been involved in upgrading not one or two majors but from 8.x to the latest and presumably greatest 13.0.1. After removing calls to obsolete methods, removing duplicate and explicitly added mappings of child types that previously was inferred. The migration was done. The confidence was high as the unit tests that verified the mapping configuration passed:
new MapperConfiguration(cfg => cfg.AddProfile<Profile>())
.AssertConfigurationIsValid();
A few seconds after the code was deployed errors started to appear in the application log.
That's strange.