Example of how to use AutoMapper v5 and Simple Injector?

[rlig...@gmail.com]

Does anyone have a working example of this?

Thanks!

[Jimmy Bogard]

How would you like to use it with Simple Injector, what lifecycles do you want for the configuration and mapper instances? Here's one way:

https://gist.github.com/jbogard/26c1f63b5efb8ff008850587b295a3a7

On Mon, Jul 18, 2016 at 2:15 PM, <rlig...@gmail.com> wrote:

Does anyone have a working example of this?

Thanks!

--
You received this message because you are subscribed to the Google Groups "AutoMapper-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to automapper-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Raine Lightner]

This is how I implemented it earlier, and any call to Mapper.Map would fail saying it didn't recognize the mapping.

Do I need to passing in the IMapping via my constructor now?

-Raine

[Jimmy Bogard]

Oh if you're doing it statically, why would you use SimpleInjector at all? Just call Mapper.Initialize and Mapper.Map.

[Raine Lightner]

I guess that's what I'm trying to figure out. Should I stick with Static or integrate all the way with SimpleInjector :)

[Jimmy Bogard]

So concretely, the reason why you'd want to integrate with SimpleInjector is that you have custom resolvers or type converters that need DI. You're never going to mock IMapper in a unit test, so there's no reason to introduce that dependency just for testing. You'd have it because an IMapper would get created with a callback to instantiate resolvers etc. via the container.

[Raine Lightner]

Jimmy, thanks again for the feedback. Totally right about not mocking IMapper, so I've left it out of my DI world :)

-Raine

[Jimmy Bogard]

I'm writing a blog today about this since it comes up often. Hopefully it answers your questions!