(from memory) mcs syntax and command line parameters are fairly different than csc so, if you are a developer familiar with mono, you won't know the correct syntax for the parameters if they are done in a csc sort of way. Plus, the compilers don't support exactly the same set of features, so to put the options all in one would force nant to have the least common denominator.
Off hand, I would think that if mcs and csc both support references and filesets, with excludes, it would be easier to allow the developer to specify the compiler. FWIW, the ide's that support mono, SharpDevelop(does it?) and Eclipse(which uses Ant) with a plugin, have you specify the compiler. --- "Shaw, Gerry" <[EMAIL PROTECTED]> wrote: > In an effort to one up people I'm going to try to get nant working under > mono on my iBook (OS X). > > My vision is for the core nant distribution to work on any .NET platform > with platform specific tasks in different dll's. I think a global > property should control what compiler the <csc> task uses. For example, > > <property name="csc.program" value="/usr/local/bin/mcs"/> > <property name="csc.style" value="Mono"/> > > <property name="csc.program" > value="C:\windows\Microsoft.NET\Framework\v1.0.3705\csc"/> > <property name="csc.style" value="Microsoft"/> > > <property name="csc.program" value="??"/> > <property name="csc.style" value="DotGnu"/> > > By default the <csc> task should work out of the box (ie, MS on Windows, > Mono on Linux) but there should be a clean way to override the compiler. ------------------------------------------------------- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
