Trying to add AutoMapper to .NetCore1.1 - not recognising services.AddAutoMapper()

Question

I've installed the following Nuget packages into my project:

Automapper
AutoMapper.Extensions.Microsoft.DependencyInjection

I have added the line to ConfigureServices in Startup.cs.

public void ConfigureServices(IServiceCollection services)
{
    // Add framework services.
    services.AddMvc();
    // . . .
    services.AddAutoMapper();
}

I'm still getting a red line under services.AddAutoMapper(). It says:

The Call is ambiguous between the following methods or properties: ServiceCollectionExtensions.AddAutoMapper(IServiceCollection, params Assembly[]) and ServiceCollectionExtensions.AddAutoMapper(IServiceCollection, params Type[])

Why is this happening? All the .NET Core add automapper guides I've read show to do it this way.

If I am not mistaken, you are using project.json. Is that right? — Shaun Luttin, Mar 21 '17 at 00:55
I tried targetting `.Net Core 1.0` and still came up the error. I'm originally targetting `1.1 ` — magna_nz, Mar 21 '17 at 01:12
check this one http://stackoverflow.com/questions/41220742/setting-up-automapper-5-1/41221647#41221647 — Ahmar, Mar 21 '17 at 04:20

score 62 · Answer 1 · answered Mar 08 '18 at 19:07

62

I just ran into this problem and came to know that You need to include following Nuget package AutoMapper.Extensions.Microsoft.Dependencyinjection

answered Mar 08 '18 at 19:07

Ikram Shah

1,206
1
11
12

3

The question states that they have already included this Nuget package. – Richard Garside Nov 26 '19 at 08:38

Robert Massa · Answer 2 · 2017-03-21T11:34:35.610

27

I'm running into the same issue, so checked the sourcecode and tests for guidance. It seems you need to pass either an assembly or a "marker type" inside the assembly you want scanned. I went for the following as my Profile classes are in the same assembly as the Startup class.

services.AddAutoMapper(typeof(Startup));

edited Mar 21 '17 at 11:34

answered Mar 21 '17 at 11:24

Robert Massa

4,345
1
32
44

What do you add if your profile classes are not in the same assembly ? – Choco Oct 13 '17 at 01:22
2

`typeof(ATypeInTargetAssembly)` – Robert Massa Oct 15 '17 at 18:35
Yep, that's what I did in the end and it worked... I found you can also add a list of these, thus allowing for multiple dependencies being configured. Might be helpful for others reading these comments to know this. – Choco Oct 16 '17 at 00:24
4

As Ikram Shah's answer points out... adding the nuget pkg `automapper.extensions.microsoft.dependencyinjection` is the answer to resolving extension method `AddAutoMapper()` when configuring services in `Startup.cs` like `services.AddAutoMapper();` – Adam Cox Apr 23 '18 at 19:57
You can use something like this: services.AddAutoMapper(typeof(AutoMappingProfile).GetTypeInfo().Assembly); – Avjol Sakaj Feb 13 '20 at 13:09

score 11 · Accepted Answer · answered Mar 21 '17 at 01:26

Not sure why this is happening, it could very well be something to do with .NET Core 1.1 but I have found a workaround.

Instead of doing services.AddAutoMapper() in ConfigureServices, replace it with the below.

var config = new AutoMapper.MapperConfiguration(cfg =>
            {
                cfg.AddProfile(new MappingProfile());
            });

            var mapper = config.CreateMapper();
            services.AddSingleton(mapper);

Where MappingProfile() is the class in which you have your CreateMap.

score 6 · Answer 4 · edited May 26 '18 at 01:06

6

Search this in nuget you can access automap

AutoMapper.Extensions.Microsoft.DependencyInjection

edited May 26 '18 at 01:06

Stephen Rauch

47,830
31
106
135

answered May 26 '18 at 00:27

SinaNasiri

83
2
3

score 3 · Answer 5 · answered May 09 '20 at 15:15

3

Install package:

Install-Package AutoMapper.Extensions.Microsoft.DependencyInjection -Version 7.0.0

Nuget:
https://www.nuget.org/packages/AutoMapper.Extensions.Microsoft.DependencyInjection/

answered May 09 '20 at 15:15

R M Shahidul Islam Shahed

1,178
13
13

score 1 · Answer 6 · edited Aug 17 '17 at 14:15

1

I had the same problem. To solved this issue I used the following versions of AutoMapper in project.csproj:

AutoMapper Version="6.0.1"
AutoMapper.Extensions.Microsoft.DependencyInjection Version="1.2.0"

Restore all packages and finally close and open the visual studio.

edited Aug 17 '17 at 14:15

VMAtm

27,943
17
79
125

answered Jul 14 '17 at 20:15

lbegazo

51
3

score 1 · Answer 7 · answered May 27 '19 at 12:23

I had the same problem (in .NET Core 2.2, Visual Studio Code 1.34.0, Ubuntu OS) despite having installed AutoMapper package (v8.1.0) and the AutoMapper.Extensions.Microsoft.Dependencyinjection package (v6.1.0).

The problem was solved by changing version of the packages in project.csproj as follows:

<PackageReference Include="AutoMapper" Version="8.0.0"/>
<PackageReference Include="AutoMapper.Extensions.Microsoft.DependencyInjection" Version="6.0.0"/>

Somehow it looks like due to the package version mismatch.

score 1 · Answer 8 · answered Jun 21 '19 at 08:52

I had the same problem. In my case, the solution was a combination of the answers above:

download the Nuget Package for Automapper -> Automapper by Jimmy Bogard
download the Nuget Package for the Automapper Dependency Injection -> AutoMapper.Extensions.Microsoft.DependencyInjection by Jimmy Bogard
add using Automapper; in the Startup.cs file

Now service.AddAutoMapper should work correctly. You can now initialize the Automapper to your liking.

score 0 · Answer 9 · answered Apr 25 '20 at 17:59

0

Add Nuget package for automapper.extensions.microsoft.dependencyinjection Latest Stable version 9

answered Apr 25 '20 at 17:59

score -2 · Answer 10 · answered Feb 12 '18 at 12:07

-2

All you need to do is add using AutoMapper; at the top of Startup.cs file. Best of Luck!!!!

answered Feb 12 '18 at 12:07

Roman Raj Bajracharya

49
4

Trying to add AutoMapper to .NetCore1.1 - not recognising services.AddAutoMapper()

10 Answers10

Linked

Related