Re: The NUnit reference goes away with Clean builds

Kelly Anderson <[email protected]> wrote:

> On Thu, Apr 3, 2008 at 10:38 AM, Brad Stiles

>>  Export the toolset from the repository and execute the unit tests

> When you say repository, you're meaning the revision control system?

Yes.  Subversion, in my case.

> Are you saying that you put NUnit.exe into the revision control, fetch
> it and execute it from there? So, in other words, you don't have any
> of the developers or the build machine actually install NUnit with an
> MSI, but rather just fetch the files out of revision control. Is that
> what you're saying here?

Well, that's the way we *used* to do it.  We don't anymore.  Instead we 
just install it on each machine.  The build servers get the latest 
version, but everybody else makes do with what they have.  As Charlie 
pointed out, we are building and testing in the directory tree created 
by Visual Studio, so that helps us out some.

> That does seem to help, but if you got the current NUnit out of
> revision control, then why would you have to do that?

We wouldn't, if we were doing things that way anymore. :)

> I may not be understanding what you mean by toolset here. I'm still a
> bit foggy, sorry.

We used to manage *all* of our tools, NUnit, NAnt, FxCop, etc, by 
keeping them in the repo.  Even with Subversion's excellent external 
reference support, it was a pain checking them out or exporting for 
*every* project to build.

So we don't do that anymore.  Now, we install all the needed tools to 
the same location on each machine.  That way, paths don't matter.



-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace