It was mostly because we introduced a new kind of "fixture", namely
AssemblyFixture, and wanted to reuse a common fixture-level setup/teardown
while avoiding confusion.

Perhaps the history is more important.  Notice that TestFixtureSetUp _is_
defined in MbUnit.Compatibility.dll but perhaps that's not good enough.

Long term MbUnit and NUnit are diverging quite rapidly.  For example, we are
unlikely to support the NUnit constraint syntax.  Instead we have an
Assert.That(...) based on C# v3.0 expression trees.

Jeff.

On Fri, Jan 16, 2009 at 12:26 AM, Henning <[email protected]>wrote:

>
> I've always been wondering - why is that so? I've been quite excited
> about the fact, that MbUnit and NUnit seem to be quite
> "interchangable" ... but since 3.x this isn't the case anymore :(
>
>
> On 13 Jan., 16:48, [email protected] wrote:
> > It was renamed to FixtureSetUp.
> >
> > -----Original Message-----
> > From: tk <[email protected]>
> > Date: Tuesday, Jan 13, 2009 2:47 am
> > Subject: TestFixtureSetUp in MbUnit 3.0.5
> > To: "MbUnit.User" <[email protected]>Reply-To:
> [email protected]
> >
> > Hi
> >
> > Quick question is TestFixtureSetUp avaliable in MbUnit 3.0.5? I get the
> following error
> >
> > The type or namespace name 'TestFixtureSetUp' could not be found (are you
> missing a using directive or an assembly reference?)
> >
> > i have tried all combination
> > using MbUnit.Framework;
> > using MbUnit.Framework.ContractVerifiers;
> > using MbUnit.Framework.Reflection;
> > using MbUnit.Framework.Xml;
> > using MbUnit.Core;
> > using MbUnit.Properties;
> >
> > From the info i gathered it is there in version 2
> >
> > Regards
> > TK
> >
> >
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"MbUnit.User" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/MbUnitUser?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to