t: Monday, November 24, 2003 1:40 PM
Subject: Re: [nant-dev] csc /lib parameter handling
I was thinking much the same thing. If we did that we would then be
sending full paths to csc and wouldn't need to write the /lib option to
the response file at all.
Then I guess we should deci
- Original Message -
From: "Ian MacLean" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, November 24, 2003 1:40 PM
Subject: Re: [nant-dev] csc /lib parameter handling
>
I was thinking much the same thing. If we did that we would then be
sending full paths to csc and wouldn't need to write the /lib option to
the response file at all.
Ian
Right now anything added to the lib tag will only affect those
references specified as a bare file name with the asis attribu
- Original Message -
From: "Ian MacLean" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, November 24, 2003 11:55 AM
Subject: Re: [nant-dev] csc /lib parameter handling
&g
Right now anything added to the lib tag will only affect those
references specified as a bare file name with the asis attribute. so:
since the fileset will exclude all non-framework bare-file references.
Ian
Gert Driesen wrote:
Yevgeniy,
I added support for the /lib(path) option using file
Yevgeniy,
I added support for the /lib(path) option using fileset support, meaning
that you're now able to use the following build syntax in all compiler tasks
(csc, vbc, vjc, jsc) :
...
eg. to set c:\Test\Assemblies and c:\Test\References as directorie
