[Mono-devel-list] Nant / OJB.NET / Maverick.NET / NVelocity

[Todd Berman]

Yes, the DirectoryScanner.cs code is what holds up the compilation on a
mono system.

And this is a reported issue, a couple months ago when I was looking
into using NAnt, I saw on the mailing list archive a thread from someone
saying they got it working, but a compile that took 2 seconds from the
commandline with mcs took 57 seconds through NAnt.

Please, don't get me wrong, at no point was ragging on NAnt, I think it
is a great tool, with some amazing potential, and its very usable now.

With regards to the nant.exe.config file and frameworks stuff here is my
issue.

I understand the need to use that section for finding certain
applications, however, many projects just need access to csc, not the
entire suite of utilities (gacutil, ngen, resgen, etc). Debugging the
'No framework found' error is the most difficult experience I had with
NAnt, its just not very intuitive at all. That was all I meant :)

Thanks for your replies, and your suggestions :)

--Todd

> -----Original Message-----
> From: mono-devel-list-admin at lists.ximian.com [mailto:mono-devel-list-
> admin at lists.ximian.com] On Behalf Of Ben Maurer
> Sent: October 5, 2003 11:54 AM
> To: Ian MacLean
> Cc: Todd Berman; 'Met @ Uber'; 'Mono-devel'
> Subject: Re: [Mono-devel-list] Nant / OJB.NET / Maverick.NET /
NVelocity
> 
> On Sun, 2003-10-05 at 11:37, Ian MacLean wrote:
> > Does CodeDOM give us a location for system compilers as well as for
the
> > tasks in the framework sdk - gacutil, resgen etc ? note that the
> > framework sdk tools are in a different location from system
compilers (
> > csc etc ) on ms .net installations.  I don't think so. To be honest
I'd
> > rather prompt the user at install time with a list of available
> > frameworks. This is what most java ide's do btw. That would entail
> > making an installer but thats another issue.
> > Ian
> Look, what Todd and I are asking is that the simplest case, using NAnt
> to build some C# files, is handled without requireing the user to know
> anything about his system. If the user needs to use those advanced
> tools, he had better be smart enough to configure his system. However,
> if you dont need the information in all cases, just don't ask for it.
> 
> Let's be innovative here. On Windows, the path to csc, etc will always
> be the same as the path to mscorlib.dll, which you can easily get with
> reflection (and this is the path to all the other tools as well).
> 
> On Linux, you can execute "which mcs", and you will get the directory
> which is holding all the executables.
> 
> I am not saying that you need to be platform independant, but rather
> that for simple uses of NAnt it is silly to ask the user what they
know
> about their system, especially when a few minutes of thinking and a
few
> more of coding can solve the problem.
> 
> As for an installer, good luck getting that to be platform
independant.
> 
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list