Re: [nant-dev] nunit2 uses obsolete version of NUnit 2.1

2003-11-24 Thread Gert Driesen
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

Re: [nant-dev] csc /lib parameter handling

2003-11-24 Thread Gert Driesen
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) : csc ... sources ... /sources lib basedir=... includes name=... / /lib /csc

Re: [nant-dev] csc /lib parameter handling

2003-11-24 Thread Ian MacLean
Right now anything added to the lib tag will only affect those references specified as a bare file name with the asis attribute. so: includes name=myref.dll asis=true / since the fileset will exclude all non-framework bare-file references. Ian Gert Driesen wrote: Yevgeniy, I added support

[nant-dev] Re: FW: [Nant-users] solution stuff

2003-11-24 Thread Matthew Mastracci
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

[nant-dev] Re: solution task and linked VS.Net files.

2003-11-24 Thread Matthew Mastracci
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?

Re: [nant-dev] Re: solution task and linked VS.Net files.

2003-11-24 Thread Ivan Tarasov
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 Link

Re: [nant-dev] csc /lib parameter handling

2003-11-24 Thread Gert Driesen
- 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

Re: [nant-dev] csc /lib parameter handling

2003-11-24 Thread Ian MacLean
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: Re:

Re: [nant-dev] Re: solution task and linked VS.Net files.

2003-11-24 Thread Ian MacLean
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