Migrate Elsa 2 to use AutoMapper 13.0.1 to avoid conflicts about elsa-core HOT 2 OPEN

To address the issue with integrating Elsa in projects that also have package dependencies on AutoMapper, where the referenced version is >=13, causing ambiguous issues with the extension method AddAutoMapper on IServiceCollection, you should follow the guidance provided in the Stack Overflow post you mentioned.

The solution is to remove the reference to the AutoMapper.Extensions.Microsoft.DependencyInjection package, as it is no longer needed with the latest versions of AutoMapper. The functionality that was previously provided by this package is now included in the main AutoMapper package.

If you are maintaining the project, you should update the project's dependencies to remove the AutoMapper.Extensions.Microsoft.DependencyInjection package and ensure that you are using the latest compatible version of AutoMapper.

If you are not the maintainer of the project, you should reach out to the maintainers of Elsa and request that they update the dependencies accordingly. You can do this by opening an issue on the Elsa GitHub repository or checking if such an issue already exists and has been addressed.

Please note that before making any changes or submitting a pull request, it is recommended to open an issue to discuss what you would like to do. This ensures that you don't spend time working on something that might not align with the project's goals or might already be under development by someone else.

This comment was generated by Glime.

from elsa-core.

Also more info here: https://docs.automapper.org/en/latest/13.0-Upgrade-Guide.html

from elsa-core.