Doesn't it though. For ages I just assumed that you had to have files in
the same directory as the project.
Ian
Matthew Mastracci wrote:
Heh - that's really cool, but the UI truely sucks. Why don't they add
a menu item for that instead? :) I had *no* clue that even existed.
I've been manual
looks like you already decided. Thats fine. Sending full paths is good.
Ian
Gert Driesen wrote:
- 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:
Title: In case you haven't seen this yet
As the MSBuild PM, do you know if the team has considered
any interop scenarios with NAnt tasks or the NAnt framework. Is this something
that would be in the scope of the work you would consider? If not, can you
comment on the technical challenges in
Heh - that's really cool, but the UI truely sucks. Why don't they add a
menu item for that instead? :) I had *no* clue that even existed.
I've been manually hacking .csproj files to point to the same file which
tends to screw up VS.NET.
Ivan Tarasov wrote:
Hello Matthew,
when you add exist
- 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 tha
Hello Matthew,
when you add existing file to the project (in VS.NET), in the open
dialog the "Open" button has an arrow on the right side. By clicking
on this arrow you activate the popup menu in which you can choose
"Link". In that case the file is not copied, in the project the xml
attribute Lin
Make sure your COM dll is registered on the server that is building your
project.
Gerold Kathan wrote:
hi - we are trying to get our solution to build by nAnt - actually we
are not successful -> there seems to be something missing - we reference
a COM dll (BAWPublicV5) and solution task produc
Viehland, Kirk wrote:
Nant developers,
I am getting this error when I compile a VS.Net 2003 solution with an
ProductInfo file that has been linked from a parent directory.
Just as a side note - what is a Linked file within a solution? How is
one created?
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
> Right now anything added to the lib tag will only
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
This should be fixed in recent nightly builds
(http://nant.sourceforge.net/nightly/builds) ?
Can you let us know if that fixed your problem ?
Thanks,
Gert
- Original Message -
From: "Wojciech Ziembla" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 13, 2003 7:41 AM
13 matches
Mail list logo
