Does someone know if there's any way to use AutoMapper with ASP.Net Core 2.0? There's no extension for IServiceCollection.
And optional question, does anyone tryed to work with AutoMapper with .Net Framework 4.7 or .Net Standard 2.0?
-
1AutoMapper works with ASP.Net Core 2.0. Where do you get stuck exactly?Win– Win2017-09-19 15:53:39 +00:00Commented Sep 19, 2017 at 15:53
-
2Ugh! It turns out I did not added AutoMapper.Extensions.Microsoft.DependencyInjection. I've added only AutoMapper :/ @Win Thanks for help anyway :)user7100073– user71000732017-09-19 16:47:05 +00:00Commented Sep 19, 2017 at 16:47
-
Possible duplicate of How to setup Automapper in ASP.NET CoreMichael Freidgeim– Michael Freidgeim2017-12-08 06:15:53 +00:00Commented Dec 8, 2017 at 6:15
-
1A complete answer with an example click this linkIman Bahrampour– Iman Bahrampour2019-05-25 06:11:11 +00:00Commented May 25, 2019 at 6:11
Add a comment
|
3 Answers
You can create an AutoMapperProfile.cs then add to startup.cs like code below
public class AutoMapperProfile : Profile
{
public AutoMapperProfile()
{
CreateMap<Abc, AbcEntity>();
}
}
Add to ConfigureServices method in startup.cs
//Automapper profile
Mapper.Initialize(cfg => cfg.AddProfile<AutoMapperProfile>());
Comments
As mentioned above you need the AutoMapper, and AutoMapper.Extensions.Microsoft.DependencyInjection Nuget packages.
Then in your Startup ConfigureServices method if you just add the service using:
services.AddAutoMapper();
This will scan all assemblies within the execution context looking for classes that inherit the Automapper.Profile class and automatically add these to the AutoMapper configuration.
