I'm puzzling over this one some more, and it does seem to me like NAnt is broken. It won't let go of my project directory in spite of the fact I am telling NAnt its base directory should be somewhere else for the script to run.
So... Another way for us to get to NAnt might be through <exec/> which gives us more flexibility. Probably. I need to test it. On Wed, Aug 17, 2011 at 9:30 AM, Michael Powell <[email protected]>wrote: > I am receiving the error: > > NAnt 0.90 (Build 0.90.3780.0; release; 5/8/2010) Copyright (C) 2001-2010 > Gerry Shaw http://nant.sourceforge.net For more information regarding the > cause of the build failure, run the build again in debug mode. Try 'nant > -help' for more information BUILD FAILED Could not find a '*.build' file in > '<MyProjectWorkingDir />' > > When I try to run MyScript.xml through the NAnt block. > > I've read through the message here, > http://www.mail-archive.com/[email protected]/msg07952.html, > and it seems like we must name the script MyScript.build for this to work? > > However, the same NAnt script can be run from the command line with: > > nant.exe -buildfile:MyScript.xml [...] <target> > > And it works just fine apart from CC.NET integration. > > If we must rename our NAnt tools with .build extension in order for CC.NETto > be happy, so be it, but MyScript.xml doesn't seem a "build-worthy" type > of script in the sense it is one cog in a greater build process. > > Any thoughts? Suggestions? > > Thank you... >
