abp icon indicating copy to clipboard operation
abp copied to clipboard
verified publisher icon abpframework

About the AutoMapper License Change

Open hikalkan opened this issue 9 months ago • 3 comments

Hi all,

I think most of the people already know that AutoMapper is going to a license change. It is becoming a commercial product rather than an open source project.

AutoMapper is the most popular object-to-object mapping library for .NET. ABP has used it since the first version.

Details of AutoMapper's commercialization are not clear yet. We are following the situation.

If it becomes a complete commercial product, we are planning to replace it with an open-source and free project. Alternatives are available. We do that because we want to keep the core ABP Framework as open-source and free as possible and not depend on commercial products as much as possible. We will create another object mapper integration and use it in the modules.

If we will have to change AutoMapper and integrate to another library, application developers will have two options:

  • Keep using AutoMapper (probably by buying a license)
  • Migrate to the new object mapper integration. In that case, we will try to keep the migration process to a minimum. If you've used the ABP's IObjectMapper service, then the changes will be much less. You probably need to remove the ABP's AutoMapper integration package and replace the mapping configuration with the new library.

For your information.

hikalkan avatar Apr 07 '25 11:04 hikalkan

Ever consider a code generator to handle the mapping, such as Mapperly?

DonovanAGBR avatar Apr 15 '25 17:04 DonovanAGBR

Can we consider fork the last version of AutoMapper and mantain it within the ABP Community?

sephit avatar May 03 '25 17:05 sephit

Can we consider fork the last version of AutoMapper and mantain it within the ABP Community?

No :)

hikalkan avatar May 29 '25 17:05 hikalkan

The latest news is that AutoMapper has officially become commercial. Has ABP decided which library to use as a replacement yet?

izanhzh avatar Jul 03 '25 01:07 izanhzh

Popular Mapper libraries:

  • AutoMapper: A convention-based object-object mapper in .NET - docs
  • Mapperly⭐️: A .NET source generator for generating object mappings. No runtime reflection - docs
  • Mapster⭐️: A fast, fun, and stimulating object-to-object Mapper - docs
  • EmitMapper: Powerful customisable tool for mapping entities to each other
  • TinyMapper: A quick object-object mapper for .NET - docs
  • ExpressMapper: .Net open source library - lightweight, lighting fast .Net mapper to map one type of object(s) to another in automated and easy way - docs
  • AgileMapper: A zero-configuration, highly-configurable object-object mapper with viewable execution plans - docs
  • Manual mapping: Generated by MappingGenerator visual studio extension, an "AutoMapper" like Roslyn based, code fix provider that allows to generate mapping code in design time.

maliming avatar Jul 03 '25 01:07 maliming

The latest news is that AutoMapper has officially become commercial. Has ABP decided which library to use as a replacement yet?

Not yet, we will be working on it.

hikalkan avatar Jul 03 '25 05:07 hikalkan

I am closing this since we decided what to do about that: https://github.com/abpframework/abp/issues/23243

hikalkan avatar Jul 04 '25 12:07 hikalkan