Matthew,
I looked into this again, and I'm pretty sure I'm right :
The HintPath is definitely the "last resort" for VS.NET. So we should undo
your change (unless you can send me a repro).
The issue you encountered was probably due to the fact that we don't yet use
the path list in the Reference
Matthew, can you add this task to NAntContrib cvs ? Its in the NAnt patches
tracker.
But I wonder if we should change it to use a collection of target elements,
eg.
That way you can also conditionally execute a certain target. (by the way:
not sure I like t
- Original Message -
From: "Matthew Mastracci" <[EMAIL PROTECTED]>
To: "Nant-Developers (E-mail)" <[EMAIL PROTECTED]>
Sent: Wednesday, March 17, 2004 1:52 AM
Subject: [nant-dev] NAnt pedantic mode
> I've run into a number of build-script bugs today that are related to
> NAnt task proper
> I've run into a number of build-script bugs today that are related to
> NAnt task properties changing/disappearing/obsoleting/etc.
>
> What does everyone think of a command-line flag to put NAnt into
> pedantic mode? This would throw an error if any build task tried to use
> a property that didn
I've run into a number of build-script bugs today that are related to
NAnt task properties changing/disappearing/obsoleting/etc.
What does everyone think of a command-line flag to put NAnt into
pedantic mode? This would throw an error if any build task tried to use
a property that didn't exist
James C. Papp wrote:
This was also my rational of not just adding a flag to . The
task is just a dynamic form of the task's depends attribute..., in
all other respect their ultimate functionality would be identical. The
task was not meant to be used as a way to call targets, but (more
accurate
Gert Driesen wrote:
But you actually have two different "assembly folders" : you have the
assembly folder that is referenced in your project file using the
"AssemblyFolderKey" attribute of the element, eg.
...
and you have the rest of the AssemblyFolder registry keys. Perhaps VS.NET
first check
- Original Message -
From: "Matthew Mastracci" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>
Cc: "Nant-Developers (E-mail)" <[EMAIL PROTECTED]>
Sent: Tuesday, March 16, 2004 11:05 PM
Subject: Re: [nant-dev] Solution task fixes + speedups
> Gert Driesen wrote:
>
> >>3. The
Gert Driesen wrote:
3. The HintPath for a reference is now checked before the
AssemblyFolders. VS.NET checks it this way and it can break a solution
that wants to reference (using a direct assembly reference) a different
version of an assembly than might have been installed in an
AssemblyFolder
- Original Message -
From: "Matthew Mastracci" <[EMAIL PROTECTED]>
To: "Nant-Developers (E-mail)" <[EMAIL PROTECTED]>
Sent: Tuesday, March 16, 2004 10:20 PM
Subject: [nant-dev] Solution task fixes + speedups
> I've spent a bit more time speeding up the solution task and fixing
> differe
I've spent a bit more time speeding up the solution task and fixing
differences from VS.NET. Here's a short summary of what to expect with
the latest CVS:
1. We only create one AppDomain per solution build and per project
build. We were creating dozens of AppDomains per project build before.
Jeff,
You should definitely get another message using the latest nightly build.
Can you package up a zip file that allows me to reproduce this issue, and
possible also send me your build log, created using :
NAnt.exe -buildfile: -verbose -logfile:buildlog.txt
(so also send me the buildlog.txt fi
I can still see this one... With the 03/13/2004 build.
I suppose I should be using the PIA for Office rather than a manually
generated interop assembly... But I don't think that's the culprit.
- Original Message -
From: Gert Driesen
Subject: Re: [nant-dev] Error while Building solu
Hello.
Awesome job on the Solution tasks. I write bi/tri lingual applications
and I am happy to see that support added in. But, I found a little
bug.
I don't know HOW I ended up with two dependent resources files but it
would be good to correctly load them.
I have an item in a project th
Title: Message
Hi,
I have put together a little
build script to make it easier to build/ rebuild NAnt and NAntContrib.
It is pretty basic so far but if it is useful to others I can check it
in. It is attached (build-contrib.xml) for review along with a
modified NAnt.build file (target Bu
15 matches
Mail list logo
