What's the "upgrade path" from Assertion.AssertEquals ?

Question

I've inherited some unit test code which is giving me a deprecation warning because it uses "Assertion.AssertEquals":

warning CS0618: 'NUnit.Framework.Assertion' is obsolete: 'Use Assert class instead'

However, I can't see the obvious method in the Assert class that I should be using instead?

AssertEquals takes two objects and a message that can be used to report the error if there's a failure. e.g.

        Assertion.AssertEquals(
             "Enqueuing first item should set count to 1",
             1, pq.Count);

What's the equivalent method on the Assert class?

Answer 1

Assert.That(a, Is.EqualTo(b),
    "Enqueuing first item should set count to 1");

Answer 2

How about this:

Assert.AreEqual(1, pq.Count,
                "Enqueuing first item should set count to 1");

Answer 3

The answer Jon Skeet presented points to the so called "Classic" model whereas John Gietzen's answer refers to the "Constraint-based" model. Both are right and both do provide the possibility to pass a message for the case of failure.

So let me conclude this:

"Classic" model

Assert.AreEqual(1, pq.Count,
    "Enqueuing first item should set count to 1");

"Constraint-based" model

Assert.That(
    pq.Count,
    Is.EqualTo(1),
    "Enqueuing first item should set count to 1");

I prefer the latter one since it reads more like a sentence.