OK, I have removed the NUnit dependency.
I'm not 100% happy with the result, but I like it better than the
previous situation.
The actual bits of NUnit code that StorEvil uses are Assert.Fail and
Assert.Ignore.
Now what happens is that if an nunit assembly is found, it is loaded
via reflection and Assert.Fail or Assert.Ignore is invoked.
If no NUnit assembly is found, StorEvil.AssertionException or
StorEvil.IgnoreException is thrown instead.
Now the only external dependencies are on Funq and Spark.
If anyone has a problem with either of these dependencies, let me know
and we'll figure out a way to work around.
Cheers
Dave
On Aug 16, 8:06 pm, Heinrich Breedt <
heinrichbre...@gmail.com> wrote:
> just had a look, and the storevil.core still has a dependency on nunit,
> which means that it will clash my version of nunit
>
> On Tue, Aug 17, 2010 at 12:20 PM, Heinrich Breedt
> <
heinrichbre...@gmail.com>wrote:
>
>
>
>
>
> > ah cool, tx :)
>
> > On Tue, Aug 17, 2010 at 12:06 PM, David Foley <
davidmfo...@gmail.com>wrote:
>
> >> Hello.
>
> >> I'm going to remove the dependency on NUnit in the next version of
> >> StorEvil (for the production code that is, I will still use NUnit for the
> >> storevil unit tests themselves).
>
> >> This dependency is already gone from master on github.
>
> >> Cheers
> >> Dave
>
> >> On Aug 16, 2010, at 6:59 PM, Heinrich Breedt wrote:
>
> >> are you think of shouldly?
> >>
http://snappyco.de/articles/2010-02-02-shouldly
>
> >> On Tue, Aug 17, 2010 at 11:43 AM, Dru Sellers <
d...@drusellers.com> wrote:
>
> >>> Or leverage that assertions only framework. I think it is shoulda?
>
> >>> -d
>
> >>> On Aug 16, 2010, at 8:42 PM, Heinrich Breedt <
heinrichbre...@gmail.com>