|
- AutoMapper — AutoMapper documentation
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, or simply an anti-corruption layer between the domain and application layer
- Getting Started Guide — AutoMapper documentation
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 established convention, almost zero configuration is needed to map two types
- AutoMapper Documentation
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, or simply an anti-corruption layer between the domain and application layer
- AutoMapper Documentation
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
- Configuration — AutoMapper documentation
By default, AutoMapper only recognizes public members It can map to private setters, but will skip internal private methods and properties if the entire property is private internal
- Custom Value Resolvers — AutoMapper documentation
For each property mapping, AutoMapper attempts to resolve the destination value before evaluating the condition So it needs to be able to do that without throwing an exception even if the condition will prevent the resulting value from being used
- docs. automapper. org
AutoMapper will automatically reverse map "Customer Name" from "CustomerName" based on the original flattening If you use MapFrom, AutoMapper will attempt to reverse the map:
- Projection — AutoMapper documentation
Without extra configuration, AutoMapper requires a flattened destination to match the source type’s naming structure When you want to project source values into a destination that does not exactly match the source structure, you must specify custom member mapping definitions
|
|
|