ExpandoObject with Nullable types only return "HasValue"

[bsohi]

Hi,

I am using below code to set up parameter dynamically.

CallSiteBinder leftHandSideParameterName = Binder.GetMember(
    CSharpBinderFlags.None,
    condition.InternalFieldName,
    typeof(object),
    new CSharpArgumentInfo[]
    {
        CSharpArgumentInfo.Create(CSharpArgumentInfoFlags.None, null)
    });

var lhsExpression = Expression.Convert(
    Expression.Dynamic(leftHandSideParameterName, typeof(object), parameterExpression),
    dataType);

ToReadableString() is broken since I upgraded the various packages in my solution. I am not certain which assembly is causing this. It was returning same information as ExpressionTreeVisualizer before the upgrade.

Output by ReadableExpressions (in debug mode)
expandoObject => (HasValue && HasValue) && !HasValue

Output by ExpressionTreeVisualizer (in debug mode)
(ExpandoObject ) => (DateTime?).PreProjectApprovalDate.HasValue && (DateTime?).PreApprovalReviewTimerPause.HasValue && !(DateTime?).PreApprovalReviewTimerUnpause.HasValue

I tried to debug the issue and MemberAccess only returning HasValue instead of PreProjectApprovalDate.HasValue.

The strange this is it was working fine before upgrade.

.net Frameowrk 4.7.2
VS2019
MVC Web API - 5.2.7

Please advise what can be the issue?

Thx
Balwinder

[SteveWilkes]

Thanks for letting me know about this - I've confirmed it's the same underlying issue as #101, which will be fixed in the next release.

[bsohi]

Thx Steve for quick response.

Any estimated time for new release? if it will be too late, if its easy fix, can you provide the fix so i can build dll manually?

Thx

[SteveWilkes]

I'll be looking to get a new release out later today - in the meantime this branch has the fix - it's the change to InternalExpressionExtensions.cs in this PR.

[bsohi]

If you are releasing it today.. I will just wait for the new release.

Thx

[SteveWilkes]

There's one more thing I'm looking to get into this release so I haven't quite managed to get it out yet - will hopefully get it done in the next day or two.

[bsohi]

Ok. I will wait for the release.

Thx

[SteveWilkes]

This has been fixed as of v3.2, which is now available on NuGet. Cheers!