Hello,
There are two issues I've run into with NAnt recently.
The first of these is that when I wrote the VS.NET addin, I ended up
writing TaskNode classes that wrap each Task. This caused me to run into a
host of problems because there isn't enough metadata on a Task to state what
attributes
Another solution is by using an import task that replaces the taskdef
task. It would be used like this:
import assembly=NAnt.DotNetTasks.dll prefix=dotnet-/
You would then use the tasks from this assembly as follows:
dotnet-csc/
Omitting the prefix attribute just brings the tasks into
they reference that library.
Anyway thanks, I look forward to the availability of the tasks again when
you get the VisualCpp stuff going.
-Jayme
- Original Message -
From: Gerry Shaw [EMAIL PROTECTED]
To: 'Jayme Edwards' [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Monday, August 19, 2002 7:26 PM
.
- Original Message -
From: Scott Hernandez [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: 'Jayme Edwards' [EMAIL PROTECTED]
Sent: Wednesday, July 17, 2002 2:47 PM
Subject: RE: [nant-dev] Re: Visual Studio.NET Addin initial thoughs
Yep, the addin should deal directly with the document. But it would
Hi guys,
I would just like to let you know where I think the
Addin is at, and where I was trying to get it to. I put it up here specifically
so more people could benefit from it and add features, so I'm all for any
improvements you guys want to make. If you look
at the help files that come
