Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate Elsa 2 to use AutoMapper 13.0.1 to avoid conflicts #5291

Open
zetic-be opened this issue Apr 27, 2024 · 2 comments
Open

Migrate Elsa 2 to use AutoMapper 13.0.1 to avoid conflicts #5291

zetic-be opened this issue Apr 27, 2024 · 2 comments
Labels
maintenance This issue is about maintenance of the code base and related aspects

Comments

@zetic-be
Copy link

Hello,

When integrating Elsa in projects also having package dependencies on AutoMapper, when referenced version is >=13, it causes ambiguous issue when using extension method AddAutoMapper on IServiceCollection.

As this post suggest: https://stackoverflow.com/questions/78025475/asp-net-core-automapper-how-to-resolve-errorcs0121-the-call-is-ambiguous-betwe
Remove the reference to the AutoMapper.Extensions.Microsoft.DependencyInjection package - no longer needed

Could you please update to latest version of AutoMapper to fix conflicts with other integrations.

Thank you in advance

@zetic-be zetic-be added the maintenance This issue is about maintenance of the code base and related aspects label Apr 27, 2024
Copy link

glime-ai bot commented Apr 27, 2024

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.

@zetic-be
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance This issue is about maintenance of the code base and related aspects
Projects
None yet
Development

No branches or pull requests

1 participant