Replacement of .IsSameOrEqualTo() for extensions in v6.0

[CNBoland]

I'm working with an extension that uses IsSameOrEqualTo() like so:

public TObjectResultAssertion WithValue(object expectedValue, string reason = "", params object[] reasonArgs)
{
    object actualValue = ObjectResultSubject.Value;

    Execute.Assertion
        .BecauseOf(reason, reasonArgs)
        .ForCondition(actualValue.IsSameOrEqualTo(expectedValue))
        .WithDefaultIdentifier(Identifier + ".Value")
        .FailWith(FailureMessages.CommonFailMessage, expectedValue, actualValue);

    return (TObjectResultAssertion)this;
}

IsSameOrEqualTo() is now an internal in v6.0. What is a recommended replacement?

[dennisdoomen]

Since it's an internal piece of code, it was never meant to be reused outside our code base. But you can still copy the code if you really need it. Although in most cases, a simple Equals should suffice.

[jnyrup]

To elaborate a bit more, IsSameOrEquals is now mostly object.Equals() plus

• allow comparison of boxed numerics, e.g. comparing (object)1d and (object)1L, and
• optimizations to avoid boxing of value types.

[CNBoland]

@dennisdoomen That worked nicely. Thank you for the suggestion.

[Lemraj]

Hi,
I have upgraded to version 6.10.0 and just replaced IsSameOrEqualTo() with Equals() as suggested. But i am getting a System.NullReferenceException. what am i doing wrong?

        if (actualValue.Equals(expectedValue.Value))
        {
        }

[jnyrup]

With object.Equals() I guess I meant public static bool Equals(object? objA, object? objB)

So in your case Equals(actualValue, expectedValue.Value).

Here's the implementation of IsSameOrEqualTo from v5

[Lemraj]

Thanks for the quick response! your suggestion worked for me.