So far in our AutoMapper series all of the property names between the input and output objects have been the same. There are times though that the property names will not match and you will need to tell AutoMapper how to map the properties else the configuration will not be valid.
In this post, we will take a look at the AutoMapper configuration need to map between property names that do not match.
In our previous post, we used AutoMapper to convert from a entity to a view model. In our example code, it only works as expected in happy path mode where the configuration is valid and there is no way to know the configuration is not valid until we run the application.
In this post, we are going to look at how with just a few lines of code, we can write a unit test to validate our AutoMapper mapping profile.
Mapping code is boring. Testing mapping code is even more boring.
AutoMapper is a simple library built to map one object to another and takes out all of the fuss of mapping one object to another.
In this post, we will create a sample ASP.NET Core API project, install and wire up AutoMapper, and update the sample Weather Forecast Controller to return a view model that was converted from our concrete object to a view model object.