Wayne Hartell wrote:
Hi All,
We have beem using NAnt-0.85-rc3 for quite some time with Visual
Studio 2003.NET. In our build files we have been executing builds like
this:
<property name="devenvPath" value="c:\program files\microsoft
visual studio .net 2003\common7\ide\devenv.com" />
<exec
program="${devenvPath}"
workingdir="..\Development\"
commandline="/rebuild ${configuration}
${nant.project.name}.sln"
/>
[...]
The problem that I am experiencing right now, and one that is sending
me quite batty after banging my head against a wall for days is....
that the build simply DOES NOT EXECUTE using NAnt as the entry point.
[...]
Someone please tell me how to build a VS.Net 2005 solution using NAnt.
It can't be this dang hard can it?????? Why doesn't exec work like it
did for VS.Net 2003?
My only guess would be that your argument order to devenv.com is
incorrect (but then again, you say it works manually on the command
line). I'd also double-check that your working directory isn't wrong in
the end.
Here's a command that's working fine for me on at least 4 different PCs:
<echo message="Compiling Solution with Visual Studio 2005" />
<exec
program="${environment::get-variable('VS80COMNTOOLS')}..\IDE\devenv.com"
commandline="My.sln /rebuild ${build.configuration}"
/>
VS80COMNTOOLS is defined on any PC that has Visual Studio installed, so
I used it to locate devenv.com. Makes the thing work for people without
telling them to configure special environment variable or set NAnt
properties.
Kind Regards,
Wayne Hartell.
-Markus-
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
