ILMerge NUnit

24 views
Skip to first unread message

Heinrich Breedt

unread,
Aug 16, 2010, 9:42:03 PM8/16/10
to StorEvil
Would you consider ILMerging Nunit, so that i can use a different
version of nunit in the rest of my project?

Is there any difficulties that im not considering?

Btw. great tool!

Heinrich

Dru Sellers

unread,
Aug 16, 2010, 9:43:25 PM8/16/10
to stor...@googlegroups.com, StorEvil
Or leverage that assertions only framework. I think it is shoulda?

-d

Heinrich Breedt

unread,
Aug 16, 2010, 9:59:46 PM8/16/10
to stor...@googlegroups.com
are you think of shouldly? http://snappyco.de/articles/2010-02-02-shouldly
--
Heinrich Breedt

“Do not wait to strike till the iron is hot; but make it hot by striking.” - William B. Sprague

David Foley

unread,
Aug 16, 2010, 10:06:31 PM8/16/10
to stor...@googlegroups.com
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

Heinrich Breedt

unread,
Aug 16, 2010, 10:20:45 PM8/16/10
to stor...@googlegroups.com
ah cool, tx :)

Heinrich Breedt

unread,
Aug 16, 2010, 11:06:54 PM8/16/10
to stor...@googlegroups.com
just had a look, and the storevil.core still has a dependency on nunit, which means that it will clash my version of nunit

Dru Sellers

unread,
Aug 16, 2010, 11:19:47 PM8/16/10
to stor...@googlegroups.com
Yeah

-d

David Foley

unread,
Aug 17, 2010, 11:02:39 AM8/17/10
to stor...@googlegroups.com
Ah yeah, I suppose it does.

I'll look at this later today. One of the things I want to look at soon is running StorEvil on Mono, and I'm not sure if ILMerge supports that. 

For now, I might just fix the two references to NUnit to use reflection to late-bind to whatever version of NUnit is  local (if present), and remove the dependency.

Dave F

unread,
Aug 17, 2010, 6:01:58 PM8/17/10
to StorEvil
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>
Reply all
Reply to author
Forward
0 new messages