Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Elsa 2.0: Consideration to use AutoMapper.Extensions.Microsoft.DependencyInjection, instead of own implementation
See original GitHub issueI have problems with my AutoMapper profiles. As soon as I use AddAutoMapper from Elsa Core, my profiles are not found. So I replaced it with an empty function on my end and call the AutoMapper functions in my main application.
I guess it is due to the AutoMapper implementation of Elsa Core. I use AutoMapper.Extensions.Microsoft.DependencyInjection.
I could replace the implementation of Elsa with AutoMapper.Extensions.Microsoft.DependencyInjection. But I wanted to inquire first if it is desired or if someone has another idea.
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
The easiest way is to use the extension method provided by Elsa (
AddAutoMapperProfile) to add your own profiles. Elsa already registers AutoMapper, so you will want to add your profiles to that instance.Alternatively, you can configure Elsa to use a different AutoMapper instance, but then you need to make sure to also register Elsa’s profiles.
Perhaps it would be better if we simply make AutoMapper a private dependency and wrap it in a custom mapper class that is them registered with DI. This way it won’t interfere with custom applications.
Fixed in 5b84a2e7a2e0cce33501fcd02f36f2411be68619