Hi there,
I've hit a problem (bug?) using <solution> . If it can't find a reference, then NAnt throws an internal error, rather than this getting reported more nicely. This causes me a problem since Internal Errors don't get sent to the logger, and so I don't see the error appear in a CruiseControl.NET log (in CCNet we use the Logger to capture NAnt output.)
I think this would be fixed if <solution> used the <csc> task internally rather calling the csc.exe compiler directly, but that may be too much effort.
I don't think that it would be that much effort. I spent a bit of time looking at this but didn't get further. Matt will know if there are other implications with using the <csc> task internally.
On a similar note I'd lik to expand the <solution> task to handle vcproj files by deferring to <cl>, <rc> and <link> tasks. That will probably be quite some work though.
Ian
Cheers,
Mike
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
