AutoMapperAssist example

gistfile1.cs

Mapper.CreateMap<TestClass, TestClassViewModel>()
                .ForMember(dest => dest.Bar, opt => opt.MapFrom(src => src.Foo));

var map = new Mapper<TestClass, TestClassViewModel>(Mapper.Engine);

Ah, that's not a bad idea! It's actually why I created those constructors that accept a mapping engine or an AutoMapper IConfiguration instance: To make it possible to string these mappers together. You can still have a single instance of a configuration or a mapping engine, like you'd probably have using AutoMapper itself, but the mapping can still be executed behind these mappers.

If there's a "recommended" way to use AutoMapperAssist, it is to share the same IConfiguration object just like one would do with AutoMapper itself. I believe much of the cost of using AutoMapper is the CreateMap<> method, and if you use AutoMapperAssist's default constructor on the mapper, you'll pay that cost every time the mapper is instantiated. There are a number of ways to handle that, but the cleanest and simplest way might just be to load an instance of IConfiguration into your IoC container and let the mappers resolve from it.

Interesting idea, I'll have to play around with resolving an IConfiguration from my IoC