I have confirmed that removing my call when initializing Automapper indeed allows the backoffice to function. Here is an example of the call:

On application startup:

Mapper.Initialize(x => x.AddProfile<RegisterAutoMapper>());

This will call an Automapper class that will setup all my mappings.

public sealed class RegisterAutoMapper : Profile
{
    protected override void Configure()
    {
        PopulateAutoMapper();
    }

    private static void PopulateAutoMapper()
    {
        SocialNetwork.Map();

        Mapper.AssertConfigurationIsValid();
    }
}

Here is an example of the map call for SocialNetwork.

internal static void Map()
{
    Mapper.CreateMap<Avatar, SocialNetwork>()
        .ForMember(d => d.AvatarName, option => option.MapFrom(o => o.Name))
        .IgnoreAllNonExisting();

    Mapper.CreateMap<SocialNetwork, Avatar>()
        .ForMember(d => d.Name, option => option.MapFrom(o => o.AvatarName))
        .ForMember(d => d.IsActive, option => option.UseValue(true))
        .IgnoreAllNonExisting();
}

It looks like Umbraco.Core.CoreBootManager is responsible initialzing the models that are required for the back office. Currently researching if I can inherit MapperConfiguration and see if Umbraco will pick them up and work correctly.

* Bump

Hey,

I too am having this issue - is there a way I can use my own mappings with the Umbraco ones? Code similar to below - I have a feeling its doing something funny on ApplicationStarted. Anyone have any ideas?

protected override void ApplicationStarted(UmbracoApplicationBase umbracoApplication, ApplicationContext applicationContext)        {           
    MappingConfiguration.Configure();  
 }

public static class MappingConfiguration{
        public static void Configure(){
            Mapper.Initialize(m =>{
                m.AddProfile<MyProfile>();
            });
        }
    }

Thanks

Hey, 

So after further investigation, we found you shouldn't use Mapper.Initialize as this bins anything that has gone before it - we went down the path of the way Umbraco set their mappings up.

In each mapping profile, we implemented the IMapperConfiguration interface, then in the ConfigureMappings we create our map like so:

public void ConfigureMappings(IConfiguration config, ApplicationContext applicationContext)
{
       config.CreateMap<PaymentAttempt, AuthRequestBlock>().ConvertUsing<AuthRequestBlockTypeConverter>();   
}

Hope that helps someone! :)

K

Running into a similar issue here.

So just to summarize: I need to ditch all profiles, and hook up the mapping through IMapperConfigurations instead?

That kind of sucks, because I want all my assemblies to be responsible for registering their own mappings, without them knowing anything about Umbraco. That's kind of the idea about mapping profiles in the first place, isn't it?

Anyways, I'll figure something out.

EDIT

Seems like I was a bit to fast in drawing conclussions there. I was actually able to fix it pretty easily by inherriting MapperConfiguration and moving my original code to load the profiles to ConfigureMappings(IConfiguration config, ApplicationContext applicationContext).

So that means I can still use my original Profiles and leave each assembly in charge of it's own mappings.

On a side note

In newer versions of AutoMapper (sadly unsupported by Umbraco 7) AutoMapper.IConfiguration has a nifty method AddProfiles(IEnumerable<Assembly> assembliesToScan), which basically loads all profiles from the assemblies you pass in. I pulled the code from the Automapper code base and added it, with some minor changes, as an extension method. Might be of use, so here it goes:

internal static class IConfigurationExtensions
    {
        //from automapper v7 (https://github.com/AutoMapper/AutoMapper)
        public static void AddProfiles(this IConfiguration me, IEnumerable<Assembly> assembliesToScan)
        {
            var allTypes = assembliesToScan.Where(a => !a.IsDynamic).SelectMany(a => a.DefinedTypes).ToArray();

            var profiles =
                allTypes
                    .Where(t => typeof(Profile).GetTypeInfo().IsAssignableFrom(t))
                    .Where(t => !t.IsAbstract)
                    .Select(t => t.AsType());

            foreach (var profile in profiles)
            {
                me.AddProfile((Profile)Activator.CreateInstance(profile));
            }
        }
    }

is working on a reply...