FWIW, I've had great success just using the <exec /> task for
running MSBuild. It works just fine, and I can pass in any
of the parameters I want. We started using it just about 5
minutes after we started building our .NET 2.0 applications,
i.e. long enough to modify the build files to accomodate it.
Sure, <exec> works for almost everything. But I guess, you'll soon
find, you miss some features from <solution> which msbuild do not
solve. Like resolving project dependences.
I haven't had any problem resolving project dependencies. MSBuild seems
to be smart enough to navigate the hintpaths defined in the various
project files and deals with those just fine. Even the COM Interop
stuff is working just peachy keen.
Or something NAnt specific.
Like what?
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers
