Mapper not initialized. Call Initialize with appropriate configuration

Question

I get error when usinng AutoMaper for netcore 2.1 projet

Mapper not initialized. Call Initialize with appropriate configuration. If you are trying to use mapper instances through a container or otherwise, make sure you do not have any calls to the static Mapper.Map methods, and if you're using ProjectTo or UseAsDataSource extension methods, make sure you pass in the appropriate IConfigurationProvider instance. AutoMapper.Mapper.get_Configuration() in Mapper.cs, line 23

I had configed it

 public class AutoMapperConfig
{
    public static MapperConfiguration RegisterMappings()
    {
        return new MapperConfiguration(cfg =>
        {
            cfg.AddProfile(new DomainToViewModelMappingProfile());
            cfg.AddProfile(new ViewModelToDomainMappingProfile());
        });
    }
}

File DomainToViewModelMappingProfile.cs

public class DomainToViewModelMappingProfile : Profile{
      public DomainToViewModelMappingProfile(){
             CreateMap<Function, FunctionViewModel>();
             CreateMap<AppUser, AppUserViewModel>();
             CreateMap<AppRole, AppRoleViewModel>();
 }
}

File Startup.cs

 services.AddSingleton(Mapper.Configuration);
        services.AddScoped<IMapper>(sp => new Mapper(sp.GetRequiredService<AutoMapper.IConfigurationProvider>(), sp.GetService));

Anyone can help me? Thanks you!

https://github.com/AutoMapper/AutoMapper.Extensions.Microsoft.DependencyInjection — Lucian Bargaoanu, Aug 01 '18 at 04:44
check this link https://stackoverflow.com/questions/44039968/automapper-mapper-not-initialized-call-initialize-with-proper-configuration — Amin Saadati, Aug 01 '18 at 04:45

alsami · Answer 1 · 2018-08-01T07:45:13.387

6

I would suggest you to use the automapper extension for microsoft-ioc.

In your configureservice-method (startup-class):

services.AddAutoMapper(typeof(Startup).Assembly);

You don't need to configure the profiles manually then, because the extension will scan for the types in the given assembly or assemblies you pass to it.

edited Aug 01 '18 at 07:45

answered Aug 01 '18 at 05:44

alsami

8,996
3
25
36

score 2 · Answer 2 · edited Apr 02 '19 at 13:41

2

Are you using .ProjectTo<>() in any of the calls that you are doing? If yes, try to add the configuration in the parameters:

IMapper _mapper; //Inject in constructor

_repository.GetAll().ProjectTo<YourProjection>(_mapper.ConfigurationProvider);

edited Apr 02 '19 at 13:41

Paul Roub

36,322
27
84
93

answered Apr 02 '19 at 13:32

g_brahimaj

197
7
21

Just what I needed. – Ronald Ramos Jul 08 '19 at 18:48

score -1 · Answer 3 · edited Jun 20 '20 at 09:12

-1

This worked for me.

Solution

In Startup.cs, you can fix it by replacing

services.AddSingleton(Mapper.Configuration);

with

services.AddSingleton<IConfigurationProvider>(AutoMapperConfig.RegisterMappings());

Source

edited Jun 20 '20 at 09:12

Community

1
1

answered Apr 01 '19 at 02:59

Wictor Chaves

957
1
13
21

Mapper not initialized. Call Initialize with appropriate configuration

3 Answers3

Solution

Linked