Hi Scott,
Right now, the CFResGen has the same functionality and the same commandline
options. The only difference between the ResGen and CFResgen, is the name
of the executable to use and the path to that executable. So I don't think
it's a good idea to create a separate task, I think the
As per our developers:
Our compiling also requires us to use /noconfig in addition to
/nostdlib, because this causes it to include settings in the global
csc.rsp file that we don't want.
We were able to disable both in the compiler task using:
We also added the following variables:
windows.
Hi Gert,
It seems like issue #4 is the only that cannot be resolved without code
changes. As for #1 and #2 you can just use an inside of the task.
For #3 we should really get a specific task for it, but in the mean time
you should be able to use the exec task. If you would like to help, you
could
Hi,
Is support for compiling .NET Compact Framework applications (using the
.NET Framework 1.1 compilers) planned for NAnt ?
In order to support compiling applications for the .NET Compact Framework
the following changes should be implemented :
- the C# compiler task should support the /nos
This bounced, so here we go again.
> The NAnt license is the GPL. It is not a problem to run it or redist it.
If
> you want to link to it, or include it as a library (read: source
> integration), then you should read the license for those restrictions.
>
> - Original Message -
> From: "Br
Hello!
When I documenting dataset derived class with built-in NDoc, the documenting process
fail:
"C:\Projects\DataSet\Foo.build(19,10): Error reflecting against the Foo.dll assembly:
Exception has been thrown by the target of an invocation."
If I send the nant created temp file (C:\DOCUME~1\gu
