ASP.NET 4.7.1 Hosting – Mapping Similar Objects In ASP.NET Core 2.0 | ASP.NET 4.5 Hosting News (SuperBlogAds Network)

This post is about Automapper. As its name suggests, it will do some sort of mapping. Now, the question is, what sort of mapping? Well, this mapping is all about mapping the properties of two objects with each other. If you have worked on MVC, you must have come across the scenario, where the situation demands you to map properties of the model with the properties of ViewModel. Isn’t it a common scenario? So, one way to achieve this is to map each and every property manually with a lot of code, which in turn become very tedious when there are many properties of an object. Another major disadvantage of this approach is it’s error-prone.

Hence, Automapper came to rescue. Automapper is an object to object mapping which reduces the manual effort of mapping each property of a class with the same properties of another class. So, let’s start by writing some code and see how it works.

Step 1

First step is to add the required dependency. This can be done either by using UI or by using Nuget package console,

Install-Package AutoMapper.Extensions.Microsoft.DependencyInjection

1	Install-Package AutoMapper.Extensions.Microsoft.DependencyInjection

if you are using console to add dependency, then on successful installation of the package, the below message will be shown,

Step 2

Get ready with classes which are to be mapped. Here in this case, we have one model class and one ViewModel class as shown below,

Contact

public class Contact
{
public string Name { get; set; }
public string SecurityNumber { get; set; }
public string Address { get; set; }
}

ContactViewModel

public class ContactViewModel
{
public string Name { get; set; }
public string SecurityNumber { get; set; }
public string City { get; set; }
public string State { get; set; }
}

public class Contact

{

public string Name { get; set; }

public string SecurityNumber { get; set; }

public string Address { get; set; }

}

ContactViewModel

public class ContactViewModel

{

public string Name { get; set; }

public string SecurityNumber { get; set; }

public string City { get; set; }

public string State { get; set; }

}

Step 3

Create a class which will take care of all the mappings as shown below, by inheriting the profile which is defined in Automapper namespace,

public class MappingEntity:Profile
{
public MappingEntity()
{
CreateMap<ContactViewModel, Contact>();
}
}

public class MappingEntity:Profile

{

public MappingEntity()

{

CreateMap<ContactViewModel, Contact>();

}

Step 4

public void ConfigureServices(IServiceCollection services)
{
services.AddMvc();
services.AddAutoMapper(x => x.AddProfile(new MappingEntity()));
}

public void ConfigureServices(IServiceCollection services)

{

services.AddMvc();

services.AddAutoMapper(x => x.AddProfile(new MappingEntity()));

}

Step 5

Final step is to do the changes in Controller class to accomodate this mapping.

public class HomeController : Controller
{
private readonly IMapper _mapper;
public HomeController(IMapper mapper)
{
_mapper = mapper;
}

public IActionResult Index(ContactViewModel vm)
{
var contact = _mapper.Map<Contact>(vm);
return View();
}

...
}

public class HomeController : Controller

{

private readonly IMapper _mapper;

public HomeController(IMapper mapper)

{

_mapper = mapper;

}

public IActionResult Index(ContactViewModel vm)

{

var contact = _mapper.Map<Contact>(vm);

return View();

}

...

}

Now, as per the business requirement, the contact object declared in line number 11 can be used. That’s all about automapping.