Re: Installing NUnit

Mike Chess <[email protected]> wrote:

> Our developers are just beginning to introduce NUnit into our
> environment. As we were talking through some of the conflicts we had
> in installation locations, the question was raised "What about
> installing on 64-bit systems?"  The nunit.framework assembly has to
> be referenced in each Visual Studio project.  The reference would
> point to the install location of NUnit (by default C:\Program
> Files\NUnit 2.4.7\).  On 64-bit systems the default location would
> presumably by C:\Program Files (x86)\NUnit 2.4.7\.  The project with
> the nunit.framework should fail to compile on a 64-bit system as it
> would be looking for the assembly in C:\Program Files\ and not
> C:\Program Files (x86).

Hmmm, this thread looks familiar...:)

You have a couple of choices.

1.  Don't install it at all.  If your repository supports sharing of 
code, like Subversion and, presumably, CVS and others, put NUnit in your 
source code repository and reference it from each project that is using 
it, or export it from your repo when you run the tests.  We used to do 
something like this, but we have enough projects that it got to be a 
pain.

2.  Install it in some standard directory, e.g. c:\devtools\NUnit, on 
*every* machine, including your build servers.  It will always be in 
that location, so your references should work.

3.  Install the NUnit.Framework dll to the GAC.  Everything that builds 
will see it there, though you may need other pieces of NUnit to actually 
run tests.  If those other other pieces are in the same location as the 
console and/or gui runners, and that location is in your path, running 
tests shouldn't be a problem.

Brad 


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone