I am a speed freak. In everything. Cars, motorcycles, computers.. you name it. Also I love the idea of creating object to object mappings without actually writing code for mapping each field from one object to another. AutoMapper does a pretty good job doing the mappings, but does not satisfy my hunger for speed.
I covered a very basic usage of AutoMapper in a previous article here. NextMap is built with compatibility with AutoMapper in mind, so all you need to do is just change the referred assembly and the using namespace to NextMap and you are ready to compile and use the new auto mapping engine.
As for the supported features, it's just version 0.01. There is the very basic set of mappings supported, anything that can be mapped without explicit casting, Lists of Lists of Lists ... of Lists from anything that can be mapped without explicit casting... Mapping arrays of one type to another is not supported yet. But will be in v0.02 or v0.03 the latest. Mapping dictionaries is also planned for the very near future. As for the custom mappings the only supported features are rules for member mappings as Ignore() and MapFrom(). Mapping of different types are not supported: a member of type string to a member of type decimal will not succeed, there will be an exception when calling AssertConfigurationIsValid() with the message that the destination member is not mapped. If the mapping configuration for a member is done explicitly with MapFrom() and the types mapping is not supported there will be an exception.
The philosophy of NextMap is to provide safe mappings, to try to minimize developer effort and errors.
Also here is a version hosted on this domain in case you have domain restrictions NextMap v0.01