Closed simax closed 2 years ago
Hi!
Dynamic has different levels of support between runtimes - .NET Standard 1.0 supports mapping nested dynamic members, but gives the error you encountered if you try to map a dynamic object 'directly'. Here's an updated fiddle successfully mapping the dynamic as a nested member with AgileMapper v1.8.1.
I'd have thought .NET 6 would use the .NET Standard 1.3 version of the package - which supports both scenarios - so I'm not sure what's going on at runtime on .NET Fiddle. Here's the result of running the same code in a .NET 6 unit test project in VS2022:
Hope that helps!
All the best,
Steve
OK, thanks for quick response and congrats on the project.
https://dotnetfiddle.net/Dh3uCR
I'm just starting to play around with this package because it looks really useful. But I hit a problem when trying out the example regarding mapping dynamic/expando objects that I copied from the docs.
Running the code produces:
What am I missing?