Automapper: Update to 5.0 broke existing maps

[sschneider1207]

I updated from 4.1 and I get the following errors from two of our existing profiles when asserting the configration is valid:

No coercion operator is defined between types 'System.Nullable`1[System.DateTimeOffset]' and 'System.Nullable`1[System.DateTime]'.

Expression of type 'System.Nullable`1[System.Boolean]' cannot be used for parameter of type 'System.Nullable`1[System.DateTimeOffset]'

For the first one, we have a DateTimeOffset? -> DateTime? map (as well as the other way around) defined that previously worked fine, for the second I have no clue what it is talking about.

[lbargaoanu]

Try the MyGet build.

[sschneider1207]

Unfortunately I can't add an alpha package from a different nuget feed to this project.

[lbargaoanu]

Then I guess you'll have to wait...

[lbargaoanu]

This can be closed.

[jbogard]

5.0.1 is released.

[sschneider1207]

@lbargaoanu this was not fixed with 5.0.1

[jbogard]

5.0.2?

On Thursday, July 21, 2016, sschneider1207 [email protected] wrote:

@lbargaoanu https://github.com/lbargaoanu this was not fixed with 5.0.1

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/AutoMapper/AutoMapper/issues/1446#issuecomment-234253270,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGYMijL6xEA7sf8SWVkZRtPS6PF8cxwks5qX3RxgaJpZM4JFWyD
.

[sschneider1207]

Sorry didn't notice 0.2 was out, updated to it and I'm still having the same issue.

[xrkolovos]

me too

[lbargaoanu]

Try the MyGet build.

[Gaulomatic]

Does not work with 5.2.0-alpha-01226.

EDIT:
In my case this happens if both converting directions are implemented in the same class. Don't know if this is a bug or the intended behavior.

[lbargaoanu]

A repro would help. Make a gist that we can execute and see fail.

[apopovsky]

I have a repro for this issue:
https://gist.github.com/apopovsky/73e220c9cbeec4dd8d89bfdd7e4575d6

I have a similar scenario that was working before. In this case the problem is using
o.NullSubstitute() on a child object.

[lbargaoanu]

http://automapperdocs.readthedocs.io/en/latest/Null-substitution.html

[apopovsky]

In my case, me (or whoever wrote the mapping), misinterpreted the Null substitution, passing an instance of the destination type instead of the source. Changing the instantiated type fixed the mapping.
I wonder how this ever worked.
Thanks!

[lbargaoanu]

There were some changes around that, so it's possible it worked in some version.

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.