Consider supporting Automapper dependency injection

[realLiangshiwei]

Currently, we create Automapper when the application is initialized, But this way we cannot use Automapper's dependency injection function, like: https://docs.automapper.org/en/stable/Before-and-after-map-actions.html#asp-net-core-and-automapper-extensions-microsoft-dependencyinjection

abp/framework/src/Volo.Abp.AutoMapper/Volo/Abp/AutoMapper/AbpAutoMapperModule.cs

Line 30 in a130e0d

CreateMappings(context.ServiceProvider);

.

We can consider creating Automapper in advance to get dependency injection. example:

public override void PostConfigureServices(ServiceConfigurationContext context)
{
    var mapperAccessor = new MapperAccessor();

    context.Services.AddSingleton<MapperAccessor>(_ => mapperAccessor);
    context.Services.Add(new ServiceDescriptor(typeof(IMapperAccessor), CreateMappings, ServiceLifetime.Singleton));
}

private IMapperAccessor CreateMappings(IServiceProvider serviceProvider)
{
    var options = serviceProvider.GetRequiredService<IOptions<AbpAutoMapperOptions>>().Value;

    void ConfigureAll(IAbpAutoMapperConfigurationContext ctx)
    {
        foreach (var configurator in options.Configurators)
        {
            configurator(ctx);
        }
    }

    void ValidateAll(IConfigurationProvider config)
    {
        foreach (var profileType in options.ValidatingProfiles)
        {
            config.AssertConfigurationIsValid(((Profile) Activator.CreateInstance(profileType)).ProfileName);
        }
    }

    using (var scope = serviceProvider.CreateScope())
    {
        var mapperConfiguration = new MapperConfiguration(mapperConfigurationExpression =>
        {
            ConfigureAll(new AbpAutoMapperConfigurationContext(mapperConfigurationExpression,
                scope.ServiceProvider));
        });

        ValidateAll(mapperConfiguration);

        var mapperAccessor = serviceProvider.GetService<MapperAccessor>();
        mapperAccessor.Mapper = new Mapper(mapperConfiguration, serviceProvider.GetService);

        return mapperAccessor;
    }
}

[realLiangshiwei]

Or we can consider compatible https://github.com/AutoMapper/AutoMapper.Extensions.Microsoft.DependencyInjection

[hikalkan]

I didn't know this feature of the AutoMapper. While ABP has a way to use DI on the mapping, such a support would be good.

You can implement and send a PR.

[maliming]

Reported by customer
https://support.abp.io/QA/Questions/472/Injecting-service-into-AutoMapper-profile

[mtozlu]

Currently i use DI in Profile, however this issue should be implemented to allow usage of actions and native DI support of AutoMapper.
Here is how i use it for now:
In AppModule:

Configure<AbpAutoMapperOptions>(options =>
{
	options.AddMaps<PortalApplicationModule>();

	options.Configurators.Add(abpAutoMapperConfigurationContext =>
	{
		var profile = abpAutoMapperConfigurationContext.ServiceProvider.GetRequiredService<TestAutoMapperProfile>();
		abpAutoMapperConfigurationContext.MapperConfiguration.AddProfile(profile);
	});
});

Profile:

public class TestAutoMapperProfile : Profile, ITransientDependency
{
	public TestAutoMapperProfile() { }
	public TestAutoMapperProfile(ITranslatableObjectManager translatableObjectManager)
	{
		CreateMap<TestGroup, TestGroupListOutputDto>()
			.BeforeMap((s, d) =>
			{
				translatableObjectManager.Translate<TestGroup, TestGroupTranslation>(s);
			});
	}
}