Configuration of AutoMapper with ASP.NET Core

Question

In ASP.NET Core, AutoMapper is now configured like this (in Startup.ConfigureServices):

var config = new MapperConfiguration(cfg => { 
    cfg.AddProfile(new MyConfig());
});
services.AddSingleton<IMapper>(sp => config.CreateMapper());

Why not the following:

var config = new MapperConfiguration(cfg => {
    cfg.AddProfile(new MyConfig());
});
var mapper = config.CreateMapper();
services.AddSingleton(mapper);

Is there a difference? Something to do with lazy loading maybe?

First one creates the instance on first request, second during bootup — Tseng
– Tseng, Commented Nov 6, 2016 at 21:07

grokky · Accepted Answer · 2016-11-25 09:08:29Z

4

First one creates the instance on first request, second during bootup.

answered Nov 25, 2016 at 9:08

grokky

9,42523 gold badges69 silver badges104 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Configuration of AutoMapper with ASP.NET Core

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related