A convention-based object-object mapper.

Headspring Systems

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. Currently, 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.

New to AutoMapper? Check out the Getting Started page first.

Check out the Roadmap to see what I'm looking at for future releases.

General Features

Flattening
Projection
Configuration Validation
Lists and Arrays
Nested Mappings
Custom Type Converters
Custom Value Resolvers
Custom Value Formatters
Null Substitution

Samples

The source code contains unit tests and samples for all of the features listed above. To view the samples, download the source code from the link below and open the AutoMapper.sln solution.

Housekeeping

The source code is hosted at Google Code: http://code.google.com/p/automapperhome/

The discussion group is hosted on Google Groups: http://groups.google.com/group/automapper-users

See the announcement, with an overview of the features here: http://www.lostechies.com/blogs/jimmy_bogard/archive/2009/01/22/automapper-the-object-object-mapper.aspx
Last edited Feb 1 at 11:00 PM by jbogard, version 22

 

Want to leave feedback?
Please use Reviews instead.

Updating...
© 2006-2010 Microsoft | About CodePlex | Privacy Statement | Terms of Use | Code of Conduct | Advertise With Us | Version 2010.1.12.16187