When auto mapping types in Jobbr.Server and some package isn't matching correctly, Automapper will throw an exception, which then bubbles up to the implementer, which may not even use Automapper, but also won't know what exactly is mismatching, as the actual information is hidden in the LoadException.
When auto mapping types in Jobbr.Server and some package isn't matching correctly, Automapper will throw an exception, which then bubbles up to the implementer, which may not even use Automapper, but also won't know what exactly is mismatching, as the actual information is hidden in the LoadException.