How about this stuff? > I think that XML-based communication between tasks and the > trycatch task have different purposes. Specifically, > trycatch is a flow control device. Flow control can > certainly be reproduced with increased task verbosity, but > using a flow control device to describe flow conveys much > more intent, which makes build files (IMHO) easier to read... > or rather, easier to interpret correctly.
Hmm. I think inter-task communication could be used for flow control as well. But no problem with trycatch task :) Currently there is resultproperty of <exec> task as only way to get result from any task (except of onfailure but it is not very useful on large build scripts). I think this should be enhanced to be able to read stdoutput/stderr for execed program and even more - number of compiled projects from <solution> etc. I hope something like this will get in 1.0 timeframe Martin ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
