I was trying to map 2 kinds of exceptions (one from an external lib to a type that belongs to my application):
CreateMap<PermissionException, MyException>()
.ForMember(dest => dest.Error, opt => opt.MapFrom(src => src.Error))
;
This would create an exception with the following message :
Instance property 'Current' is not defined for type 'System.Collections.IDictionaryEnumerator'
This exception happens whatever exception I'm trying to map.
A bit of debugging got to the point where I found that the Data
member was the one having issues. So I changed my mapping configuration to this:
CreateMap<PermissionException, MyException>()
.ForMember(dest => dest.Error, opt => opt.MapFrom(src => src.Error))
.ForMember(dest => dest.Data, opt => opt.Ignore())
;
Which seems to fix the issue.
I've looked around and there does not seems to be anything special that needs to be done for mapping exception. So I'm wondering if this is a bug or if there is something I'm doing wrong ?
Thanks for your insights.
question from:
https://stackoverflow.com/questions/65829943/automapper-10-error-when-trying-to-map-exceptions 与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…