Which is why the mcs task should go and we use the same csc task for both. The stuff i'm working on with loading settings from the confiog will allow this. Ie if you set the current runtime to be mono - it will know to call mcs.exe instead of csc.exe
Makes sense to me as long as there aren't unique mcs features somebody wants to call.
It supports all the same command line options as csc. If there are extra ones then there is always <arg>. I have the <cscTask> working with mcs now ( not checked in though ).
I got NAnt.Core, NAnt.exe and NAnt.DotNetTasks (partially) compiled last night.cool. It will be good to know which areas have issues on mono.
I still have a problem with parsing the uri with -buildfile to work through
and the figuring what I missed with the ProjectHelp.xslt resource file. Hopefully, this weekend I can get to the NUnit tests and run them from the NAnt
build file.
Ian
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
