[Mono-devel-list] [PATCH] Fix "neutral" sorting in DataView

Eyal Alaluf eyala at mainsoft.com
Thu Jul 21 12:57:56 EDT 2005


BTW, it's better to write your tests without inheriting from Assertion (which is deprectaed).
You just use the [TestFixture] attribute and go on. For an example see:
  trunk/mcs/class/System.Data/Test/System.Data/DataSetTest2.cs

Eyal.

On Thu, 21 Jul 2005, Marc Haisenko wrote:

> Date: Thu, 21 Jul 2005 17:27:41 +0200
> From: Marc Haisenko <haisenko at webport.de>
> To: mono-devel-list at lists.ximian.com
> Subject: Re: [Mono-devel-list] [PATCH] Fix "neutral" sorting in DataView
>
> On Thursday 21 July 2005 17:18, Atsushi Eno wrote:
> > Hi Marc,
> >
> > > Oh dear... luckily I now managed to write the stuff today. I've wasted
> > > two and a half hours just for that silly test ! Would anyone care to
> > > explain to me why the line
> > > Assert.AreEqual (1, 2, "Foo");
> > > causes mcs to complain "error CS0119: Expression denotes a `method
> > > group', where a `variable', `value' or `type' was expected" ?
> >
> > Because there is both Assert class and Assert method in that scope.
> > Since the test class is derived from Assertion, it guesses "Assert"
> > is NUnit.Framework.Assertion.Assert method, not NUnit.Framework.Assert
> > class.
>
> Aaaaaah, thanks a lot :-) But I guess a better error message should be
> displayed here, it'd be better if mcs would complain about ambiguity. I
> didn't had (and still don't have) an idea what a "method group" is supposed
> to mean.
>
> > So if you want to use static Assert methods, you can use alias by
> > using statement, like:
> >
> > 	using AssertType = NUnit.Framework.Assert;
> >
> > and call AssertType.AreEqual().
> >
> > Atsushi Eno
>
> Thanks for the explanations,
> 	Marc
>
> --
> Marc Haisenko
> Systemspezialist
> Webport IT-Services GmbH
> mailto: haisenko at webport.de
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>




More information about the Mono-devel-list mailing list