Home > Back-end >  How to fix: Automapper 11 with conflict dependency
How to fix: Automapper 11 with conflict dependency

Time:03-29

After upgrade of Autommaper from 10 to the latest v.11 and Automapper.Collection to the latest v.7 it appears there is a conflict.

Is it by design? Should I worry that it might cause problems in future? How to fix it?

enter image description here

CodePudding user response:

Those package versions are incompatible. If you need the collections package, you must use AM 10. See https://github.com/AutoMapper/AutoMapper.Collection/issues/162

  • Related