My team and I were in a similar boat with nAnt and VS.NET, however
having struggle so much with VS.NET and how it handles solutions and
projects, we choose to maintain nAnt build scripts to do our build and
deploys to our three different server environments.
Developers still use VS.NET to build an
I found this in the nant-developers archive, and it
helps:
RE: [nant-dev] Behavioral differences between NUnit V2.0.6 and
th e task
"...As a workaround, you can qualify
the path with: ${nant.project.basedir}. This does not change the path and
is evaluated correctly. ... "
so instead of
Oops, I just replied the message to Anananda instead of posting it to the
list.
Btw I hope someone takes a closer look at what lies beneath this "nunit
paths to assemblies" problem.
- Original Message -
From: "arjen stolk" <[EMAIL PROTECTED]>
To: "Ananda Chaudhuri" <[EMAIL PROTECTED]>
Sen
