How to setup AutoMapper in ASP.Net Core 6

Question

How to configure AutoMapper in ASP.Net Core 6

I have a project which is written in .Net 3.1 so we had Startup.cs class.

I am migrating it to .net core 6

now when I put the following configuration in my .Net 6 Program.cs

             builder.Services.AddAutoMapper(typeof(Startup));

I get error the type or namespace Startup could not be found

Any suggestions ?, how can I fix it or configure it in .net 6

`typeof(Program).Assembly` I referred [this question](https://www.reddit.com/r/dotnet/comments/pz6xmx/setting_up_automapper_in_minimal_api/) — Tiny Wang, Feb 22 '22 at 05:26
Your comment is correct, you can post it as Answer so I can accept it. — MJ X, Feb 23 '22 at 05:26

score 39 · Answer 1 · edited Feb 04 '23 at 02:20

39

install package

dotnet add package AutoMapper.Extensions.Microsoft.DependencyInjection

in Program.cs

builder.Services.AddAutoMapper(AppDomain.CurrentDomain.GetAssemblies());

create MappingProfiles.cs

namespace XXX.XXX.Helpers;

public class MappingProfiles: Profile {
    public MappingProfiles() {
        CreateMap<Address, AddressDto>();
    }
}

edited Feb 04 '23 at 02:20

davidisgeek

3
3

answered Jun 27 '22 at 03:56

sun sreng

587
6
7

score 23 · Accepted Answer · answered Feb 23 '22 at 05:35

23

Using this line instead: typeof(Program).Assembly

answered Feb 23 '22 at 05:35

Tiny Wang

10,423
1
11
29

9

You can drop the `.Assembly` bit and it'll work just [the same](https://github.com/AutoMapper/AutoMapper.Extensions.Microsoft.DependencyInjection/blob/986267d95da70fef4c4811b59065533137bdd304/src/AutoMapper.Extensions.Microsoft.DependencyInjection/ServiceCollectionExtensions.cs#L46-L47). – Daniel Liuzzi Mar 20 '22 at 13:38

score 18 · Answer 3 · answered May 08 '22 at 14:13

For those who didn't know like me.

Install AutoMapper extension for DI via NuGet or by dotnet add package AutoMapper.Extensions.Microsoft.DependencyInjection
Then in the Program.cs file register the service with: builder.Services.AddAutoMapper(typeof(<name-of-profile>)); (In .NET 6 we no longer have the StartUp.cs)

I used Profiles to do my mapping configuration. Here's a link from Automapper about profiles.

score 1 · Answer 4 · edited Jun 14 '23 at 12:16

1

Use this line to fix:

builder.Services.AddAutoMapper(typeof(Program));

edited Jun 14 '23 at 12:16

Arsman Ahmad

2,000
1
26
34

answered Apr 08 '22 at 13:23

Islam Helmy

11
1

Isn't this essentially the same suggestion as that provided by [a previous answer](https://stackoverflow.com/a/71216238/3025856)? You root this off a different persistent class (`Program`, not `Startup`), but the basic concept is the same. – Jeremy Caney Apr 09 '22 at 00:06

score 0 · Answer 5 · answered Feb 22 '22 at 05:15

0

Install AutoMapper Package(version as per your proj requirement)

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

after that register a service in CinfigureServices on Startup.cs

using AutoMapper;
public void ConfigureServices(IServiceCollection services){
    services.AddAutoMapper(typeof(Startup));
}

answered Feb 22 '22 at 05:15

Vikas

71
10

1

Core 6.0 don't have class Startup.cs – Adam G. Nov 06 '22 at 15:32

score 0 · Answer 6 · edited Jun 14 '23 at 15:16

0

Try to add this line of code in your Program.cs.

services.AddAutoMapper(Assembly.GetExecutingAssembly());

edited Jun 14 '23 at 15:16

Arsman Ahmad

2,000
1
26
34

answered Nov 28 '22 at 19:46

zied ben hadj amor

1

1

As it’s currently written, your answer is unclear. Please [edit] to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Dec 01 '22 at 00:48

How to setup AutoMapper in ASP.Net Core 6

6 Answers6