`Argument 2: cannot convert from 'System.Type' to 'System.Action<AutoMapper.IMapperConfigurationExpression>'`

[khteh]

services.AddAutoMapper(typeof(MyProfile));

Can you please provide more details how to fix this!?!

Is this https://docs.automapper.io/en/latest/Dependency-injection.html for your own internal developers!?! What's profileAssembly1 and/or ProfileTypeFromAssembly1!?!

[jbogard]

I need to update the docs here, but you need to use AddMaps instead here. All the configuration options were consolidated into the single method/configuration object.

[jbogard]

Fixed with the 15.0.1 release.

[AboubacarSow]

Just to help clarify the root cause of the issue:

In AutoMapper v15.0.1, the following line no longer compiles:

      builder.services.AddAutoMapper(typeof(AssemblyReference).Assembly);

This results in the compile-time error:

CS1503: Argument 2: cannot convert from 'System.Reflection.Assembly' to 'System.Action<AutoMapper.IMapperConfigurationExpression>'

This code used to work in v14.x, where an overload existed like:

      AddAutoMapper(params Assembly[])

In v15.0.1, the number of AddAutoMapper() overloads has been reduced from 11 to 8, and this overload was removed (intentionally or not).

✅ Workaround:

To fix the issue in v15.0.1, use:

services.AddAutoMapper(cfg => cfg.AddMaps(typeof(AssemblyReference).Assembly));

If this change was intentional, it would help a lot to mention it in the changelog or documentation, especially for users doing manual registration (without AutoMapper.Extensions.Microsoft.DependencyInjection).

Let me know if you'd like me to open a new structured issue with full reproduction steps and version comparison.

[jbogard]

This overload was removed intentionally because you need to supply the license key. I've documented the upgrade steps in the upgrade guide.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.