Re: The NUnit reference goes away with Clean builds
"Charlie Poole" <[email protected]>
| Newsgroups | gmane.comp.windows.dotnet.nunit.user |
|---|---|
| Message-ID | <012501c895bf$57be4a80$6401a8c0@ferrari> |
Hi Brad, > 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. I've used a compromise, where the devtools are checked out or updated by the developers only on an as-needed basis. The build server checks them out with every build, generally in a stub script that also checks out the "real" build script. Charlie ------------------------------------------------------------------------- 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