AutoMapper uses a fluent configuration API to define an object-object mapping strategy. AutoMapper uses a convention-based matching algorithm to match up source to destination values.

AutoMapper is geared towards model projection scenarios to flatten complex object models to DTOs and other simple objects, whose design is better suited for serialization, communication, messaging, …

What makes AutoMapper interesting is that it provides some interesting conventions to take the dirty work out of figuring out how to map type A to type B. As long as type B follows AutoMapper’s …

AutoMapper is geared towards model projection scenarios to flatten complex object models to DTOs and other simple objects, whose design is better suited for serialization, communication, messaging, …

To light them up, you need to add an using for AutoMapper.Internal and call the Internal extension method on the configuration object. Most users don’t need these advanced methods.

AutoMapper will skip open generic type maps during configuration validation, since you can still create closed types that don’t convert, such as Source<Foo>->Destination<Bar> where there is no …

Overall this feature should make using AutoMapper with classes that leverage inheritance feel more natural.

Member-based attributes are declared in the AutoMapper.Configuration.Annotations namespace. If the attribute-based configuration is not available or will not work, you can combine both attribute and …

How do I use AutoMapper? First, you need both a source and destination type to work with. The destination type's design can be influenced by the layer in which it lives, but AutoMapper works best …

By calling ReverseMap, AutoMapper creates a reverse mapping configuration that includes unflattening: