Adhesive vs Automapper vs Emit vs ValueInjecter

I am working on a DDD project where a lot of field mapping takes place. I am looking for a fast and robust mapping library, rather than recording all the mappings manually, and there seem to be a lot of options.

At the moment, I am more inclined to Clay, because it looks quite functional, and is also built taking into account unit testing, which is also important for the project I'm working on. At the bottom, it was only loaded 200 times, which makes me think that something like ValueInjecter might be a better choice, since there is more support for it.

My question is, is Clay better or worse than any of them? Or are the differences between the above markers insignificant in terms of performance and usability?

+4
source share
1 answer

Personally, I would go with AutoMapper or ValueInjector . I have used before, and they are very fast and stable. Depending on your needs, there are things that ValueInjector does, which AutoMapper does not (how easy comparisons are from left to right and right to left), so I suspect that ValueInjector may be the most suitable.

The statement that Clay is built using unit testing in this case should not affect your decisions, since you are most likely to use assemblies through NuGet and, thus, use assembled assemblies, rather than building from source code.

+6
source

All Articles