AutoMapper

AutoMapper 16.1 and MediatR 14.1 Released

Today I released AutoMapper 16.1 and MediatR 14.1 (as part of now regular quarterly releases): * AutoMapper Release Notes * MediatR Release Notes AutoMapper added some interesting features, allowing for factories and conditions to use dependencies (previously only allowing Func-based callbacks. On the MediatR side, we added support for more

AutoMapper

AutoMapper 16.0.0 and MediatR 14.0.0 Released with .NET 10 Support

With the release of .NET, we've released updated packages of AutoMapper and MediatR targeting .NET 10 (and all supported versions of .NET and 4.x of .NET Framework). From this release forward, we're aligning to major release cadences of .NET since this also means upping our

AutoMapper

AutoMapper 15.1 and MediatR 13.1 Released

Starting a new policy of regular quarterly releases, today I pushed out new versions of AutoMapper and MediatR: * AutoMapper 15.1.0 Release Notes * MediatR 13.1.0 Release Notes The previous versions restored netstandard2.0 support across the board. In these releases, I'm including first-class support for

AutoMapper

AutoMapper and MediatR Roadmaps

One of my main goals of commercialization of AutoMapper and MediatR was being able to finally invest time in these projects where basically all new work stopped when I lost corporate sponsorship. I wanted to take some time to share where I'd like to take these projects now

AutoMapper

AutoMapper and MediatR Commercial Editions Launch Today

Today I'm excited to announce the official launch and release of the commercial editions of AutoMapper and MediatR. Both of these libraries have moved under their new corporate owner (me), Lucky Penny Software. I formed this company to house these projects separate from my consulting company, but it&

AutoMapper

AutoMapper and MediatR Licensing Update

In my last post, I shared the news that I've decided to take a commercialization route for AutoMapper and MediatR to ensure their long-term success. While that post was heavy on the motivation, it was intentionally light on the details. I did share that I wanted to be

AutoMapper Featured

AutoMapper and MediatR Going Commercial

Yes, another one of "those posts". But tl;dr: In order to ensure the long-term sustainability of my OSS projects, I will be commercializing AutoMapper and MediatR. I did not post this on April 1st for obvious reasons. But first a little background on how I got to

AutoMapper

AutoMapper 14.0 Released

I pushed out version 14.0 (!) of AutoMapper over the weekend: * Release notes * NuGet This release targets .NET 8 (up from .NET 6 from the previous release). It's mainly a bug fix release, with some quality-of-life improvements in configuration validation where we gather up all the possible validation

AutoMapper

AutoMapper 13.0 Released

Today I pushed out AutoMapper 13.0 (is that too many...?): * Release Notes * Changelog * NuGet * Upgrade Guide Probably the biggest change with this release is folding in Microsoft.Extensions.DependencyInjection support directly. The AutoMapper.Extensions.Microsoft.DependencyInjection package is deprecated as a result. Side note, the docs were messed up

AutoMapper

Dissecting AutoMapper Programming Horror

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>

AutoMapper

AutoMapper 11.0.0 released

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

AutoMapper

AutoMapper LINQ Support Deep Dive

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

AutoMapper

AutoMapper 9.0 Released

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

AutoMapper

AutoMapper 8.1.0 Released

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,

AutoMapper

AutoMapper's Design Philosophy

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

AutoMapper

AutoMapper Usage Guidelines

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

AutoMapper

AutoMapper 8.0.0 Released

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

OSS

Contoso University Examples with CQRS, MediatR, AutoMapper and more

I was a bit surprised yesterday to see Scott Hanselman's post on my Contoso University sample app. That application basically takes the traditional Contoso University sample applications (of which there have been many), and try to adapt it to how our "normal" ASP.NET applications are

AutoMapper

AutoMapper extensions for Microsoft DI 5.0 released

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

AutoMapper

AutoMapper 7.0 Released

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

AutoMapper

AutoMapper 6.2.1 Released

Release notes here. The previous release introduced some inadvertent breaking behavior changes in convention-based map creation and some DI scenarios. This maintenance release fixes these two issues by: * Allowing configuration of member lists to validate per-map * Allowing resetting of static mapper configuration (for testing scenarios) Find this release on NuGet: