Need a small improvement to the flatten name matching about expressmapper HOT 6 CLOSED

@JonPSmith Any thoughts on this? I noticed you were the one who implemented Flatten, you might have an answer for me :)

from expressmapper.

Hi @RudeySH,

The flattening I added is fairly basic, but I have written a long article that explains how it works.

I was planning to change from AutoMapper to ExpressMapper, but two things have stopped me from doing that:

• ExpressMapper isn't updated very often. Specifically it isn't currently usable with .NET Core (see issue #143 and #135). AutoMapper is very well supported.
• AutoMapper has significantly improved its initial set up performance, which was the problem that made me look at ExpressMapper.

from expressmapper.

Thanks @JonPSmith . In the meanwhile I have done some experimenting with ExpressMapper and I already feel like I should switch to AutoMapper because of all the issues I'm running in to.

Slightly off topic, but are the performance tests between ExpressMapper and other mappers purely focussed on the initial set up performance? I will maily be using mapping for EF queries and I am worried that AutoMapper will slow my queries down.

from expressmapper.

Hi @RudeySH,

It was a while ago but ExpressMapper and AutoMapper LINQ->EF were the same. They should produce similar LINQ and its then up to EF to convert it.

from expressmapper.

It turns out this is pretty easily done in AutoMapper. AutoMapper/AutoMapper#2489

from expressmapper.

Good to know. Thanks.

from expressmapper.