Re: The NUnit reference goes away with Clean builds

Hi Kelly, 

> If NUnit isn't installed, then how do you run your tests? Do 
> you reinstall NUnit as part of your build process? If so, 
> then how do you do your build?
> 
> Perhaps my question wasn't clearly stated, I'm not building 
> NUnit, I'm using NUnit in my build to run NUnit tests as part 
> of my continuous integration. When I do a clean, the 
> references to NUnit inside my Test projects get messed up. 
> I'm trying to figure out how to set it up so that those 
> references don't get blown away.

Yes, that was understood. What I'm saying is that NUnit does
not require installation via the MSI. You just need to have
a copy of it somewhere that you reference from your tests
and which you use to run the tests. You can just put it into
source control in some sort of tools directory, which you 
update as needed on the server.

Doing a clean shouldn't change the references in your project,
although it will remove the copies of nunit.framework that
are in your bin directories, so that may be what you meant.
I don't have this problem, since I don't run builds on the
server in my source tree - I generally copy to a deployment
directory first. Since copying the framework is a step in
the build/test process, it's always there.

Brad describes an alternate approach which may work better
if you are testing right in the VS source tree.

Charlie
 
> -Kelly
> 
> On Wed, Apr 2, 2008 at 7:26 PM, Charlie Poole 
> <[email protected]> wrote:
> > Most teams I work with don't install NUnit at all - they just  
> > download the binary zip and put it into source control.
> >  In fact, that's why that particular package was created.
> >
> >  Charlie
> >
> >
> >
> >  > -----Original Message-----
> >  > From: [email protected]
> >  > [mailto:[email protected]] On 
> Behalf  > Of 
> > Kelly Anderson  > Sent: Wednesday, April 02, 2008 3:07 PM  > To: 
> > [email protected]  > Subject: [Nunit-users] 
> The NUnit 
> > reference goes away with Clean builds  >  > In our build system, 
> > whenever we do a clean, it blows away  > the reference to 
> NUnit in the 
> > project. To get it to build  > again, we have to manually add the 
> > reference in again. Part  > of the problem might be that the team 
> > upgrades NUnit at an  > uneven pace, so we turn the 
> "Specific Version" 
> > flag off in  > the properties of the reference.
> >  >
> >  > It may be that NUnit's decision to have a different directory  > 
> > every time an upgrade is installed is part of the problem. 
> Do  > you 
> > install NUnit in it's default directory, or do you always  
> > install 
> > it in an NUnit directory or something like that?
> >  >
> >  > It seems strange to me that we would be having problems with  > 
> > this, and I'm wondering if anyone has a recommended  > 
> workaround for 
> > this issue.
> >  >
> >  > Thanks!
> >  >
> >  > -Kelly
> 
> --------------------------------------------------------------
> -----------
> 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.n
> et/marketplace
> _______________________________________________
> Nunit-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/nunit-users
> 



-------------------------------------------------------------------------
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