My AutoMapper search alerts brought me this gem this morning: Hey... let's use automapper to generate passwords. This post illustrates basically all the wrong reasons to use AutoMapper. Here's the code minus the unimportant bits: public class RequestProfile : Profile { public RequestProfile() { CreateMap<Request, NewAccount>

As the title says, I pushed AutoMapper 11.0.0 today: * Release notes * NuGet * 11.0 Upgrade Guide This is somewhat of a minor release but some API changes forced a major version bump. Also, starting with this version, AutoMapper drops support for full .NET framework, as this release targets

My favorite feature of AutoMapper is its LINQ support. If you're using AutoMapper, and not using its queryable extensions, you're missing out! Normal AutoMapper usage is something like: var dest = _mapper.Map<Dest>(source); Which would be equivalent to: var dest = new Dest { Thing

As with the other major releases of AutoMapper, this one introduces breaking API changes with relatively few other additions. The major breaking changes (see upgrade guide for details) include: * Removing the static API * Removing "dynamic" maps (automatically created maps) * Fix on IMappingAction to include a ResolutionContext parameter The

Today we released AutoMapper 8.1.0: * Upgrade Guide for 8.0 * Release Notes AutoMapper 8.1 adds a major new feature - attribute-based maps. Attribute maps let you easily declare maps on destination types when you have straightforward scenarios. Instead of: public class OrderProfile { public OrderProfile() { CreateMap<Order,

While a lot of people use AutoMapper, and love it, I meet just as many people that hate it. When I hear their stories, it becomes clear to me that it's not that AutoMapper was "abused" per se, but that it was used without understanding why

Configuration √ DO initialize AutoMapper once with Mapper.Initialize at AppDomain startup in legacy ASP.NET AutoMapper's static initialization is designed to build configuration once, and cache it. √ DO use the AutoMapper.Extensions.Microsoft.DependencyInjection package in ASP.NET Core with services.AddAutoMapper(assembly[]) The extensions package will perform

Today we released AutoMapper 8.0.0: * Upgrade Guide * Release Notes AutoMapper 8.0 brings some breaking API changes, meant to simplify our configuration options which have grown quite a bit over time and remove some confusion about what configuration options were effectively equivalent. The upgrade guide walks through the

Hot off the presses, with some pretty big breaking changes. For the unfamiliar, the AutoMapper.Extensions.Microsoft.DependencyInjection package is the extension to the MS DI libraries used by ASP.NET Core and others. It lets you do: services.AddMvc(); services.AddAutoMapper(); And this package finds all AutoMapper configuration in

Today I pushed out the AutoMapper 7.0 release: Release notes This release is mainly bug fixes, but keeping with the last few major releases, has a few breaking API changes. The major breaking API change is breaking out the expression mapping (OData support) so that it can release independently