--- Ian MacLean <[EMAIL PROTECTED]> wrote: > 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. While your at it.... VolumeInfo.cs is going to be a problem under linux. My problems with wine (a quasi mswin32 api compatibility layer for linux that allows certain windows program to operate on a linux box) were actually triggered by the VolumeInfo.IsCaseSensitive call which cascades off to a bunch of dllimport supported methods. There is still a problem with Mono and wine, but if we're lucky we can avoid the problem altogether with NAnt by not requiring win32 api calls at all, at least under linux/mono. I got NAnt.Core, NAnt.exe and NAnt.DotNetTasks (partially) compiled last night. 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. ------------------------------------------------------- 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
