Hi Gerry,
> Yes, this seems like either:
> 1. We are missing something, or
> 2. A mistake.
>
> Tomas can you post (maybe just send the post you sent here) to them?
> You seem to have the most experience with the issue.
Done. I'm waiting to hear on more information. From what I can gather now,
it
> >I don't know anything about NUnit's internals, nor do I know what
they
> >pretended to do, but right now, this doesn't look good and puts a bit
> >of a showstopper in nant :(
> >
> We could try posting to the NUnit dev list and see what they say.
Yes, this seems like either:
1. We are missi
Tomas Restrepo wrote:
Hi guys...
I don't know anything about NUnit's internals, nor do I know what they
pretended to do, but right now, this doesn't look good and puts a bit of a
showstopper in nant :(
We could try posting to the NUnit dev list and see what they say.
Ian
ildfile... talk about a catch 22.
- Original Message -
From: "Tomas Restrepo" <[EMAIL PROTECTED]>
To: "'Nant-Developers (E-mail)'" <[EMAIL PROTECTED]>
Sent: Tuesday, October 29, 2002 8:34 PM
Subject: [nant-dev] NUnit2 task assemblyname attribute
Hi guys...
I've been updating tonight the NAntContrib code to use the new NUnit2 tests,
and quite quickly ran into a gotcha with the new assemblyname attibute: It
is exactly that, an assembly name, and cannot take an assembly _file_ name.
In fact, the build files for nant itself pass in an assemb
