Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Automapper issue

See original GitHub issue

Startup.cs(36,22): error CS1061: 'IServiceCollection' does not contain a definition for 'AddAutoMapper' and no accessible extension method 'AddAutoMapper' accepting a first argument of type 'IServiceCollection' could be found (are you missing a using directive or an assembly reference?)

Resolved by placing using Automapper; at the top of Startup.cs file

See https://stackoverflow.com/questions/42916182/trying-to-add-automapper-to-netcore1-1-not-recognising-services-addautomapper

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:16 (10 by maintainers)

Top GitHub Comments

18reactions

eric-wilsoncommented, Oct 26, 2020

@subhanisyed17 - I had the same problem until I added AutoMapper.Extensions.Microsoft.DependencyInjection Nuget package.

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

1reaction

fmjnaxcommented, Jan 3, 2022

If you are having issue with adding your auto mapper, It is better you check through the type and version you added. If it is not “AutoMapper.Extensions.Microsoft.DependencyInjection”, then you won’t be able to use “services.AddAutoMapper()”. Sometimes, you might mistakenly add "AutoMapper

@Sunboy005 Thanks! This was the trick for me in my Blazor WASM project. I had both AutoMapper and AutoMapper.Extensions.Microsoft.DependencyInjection. I removed the AutoMapper package and everything worked.