Closed EduardoPires closed 7 years ago
Hey guys actually i use this solution to fix this problem. I think this isn't a solution but maybe a good point to start to fix the problem. I think fluent mapper must have a more sophisticated reflection algorithms do to this.
https://gist.github.com/g-adolph/f0eb5b977006b96e12dff27c4e61212f
@g-adolph Your gist isn't available :(
Try copying the link: https://gist.github.com/g-adolph/f0eb5b977006b96e12dff27c4e61212f
@henkmollema, if I do a pull request fixing this issue will be accept? I fixed this issue and created a few tests.
@g-adolph I guess I'll take this PR in. If you would like to make one, please do.
I'm having the same issue. Is there an ETA on a release for this fix?
Thank you.
Some news about it?
Gentlemen!
Based on the discussion we had here in this thread, I took the liberty of looking at the code that @g-adolph put into the gist and implemented it.
I wrote some tests and it seems that everything really works as it should, I did this because talking to several friends of the software community including @EduardoPires we think that this bug is of great importance for the mapping of value objects with domain entities.
I'm waiting for new...
The entire explanation can be found here: http://stackoverflow.com/questions/40881195/mapping-value-objects-with-dapper
I'm trying to map a value object to my domain model. This nested VO isn't a table is just a VO in my rich domain. Simplified scenario when I get the error at application startup:
I always receive the same error at application initialization:
Index was outside the bounds of the array.
Exception Details: System.IndexOutOfRangeException: Index was outside the bounds of the array.
Using ASP.NET MVC 5, more details about the Stack Trace can be found at StackOverflow link