-Original Message-
From: Jaroslaw Kowalski [mailto:[EMAIL PROTECTED]
Sent: den 17 mars 2004 07:52
To: Matthew Mastracci; Nant-Developers (E-mail)
Subject: Re: [nant-dev] NAnt pedantic mode
I've run into a number of build-script bugs today that are
related to
NAnt task
Personnaly, I prefered tha way it worked before the changes:
-if i have a target with the depends attribute, the target(s) in the
depends are executed only if they weren't executed previously.
-having the force attribute on the call task.
But i would agree in having the force attribute to
Gert Driesen wrote:
You mean an attribute that didn't exist ? Properties that don't exist cause
a build error already ...
Yep - that's what I was thinking.
But I agree that we should indeed have this mode (or just always run NAnt in
this mode, what do you propose) ...
In what cases should NAnt
I can absolutely, 100% guarantee that this is the case. I have a
.csproj file with the following reference:
Reference
Name = C1.Win.C1FlexGrid
AssemblyName = C1.Win.C1FlexGrid
HintPath =
Gert Driesen wrote:
I can also guarantee 100% that VS.NET (2003) is only using the hintpath as a
last resort ;)
I've reverted the change in CVS. Thanks for the explanation :)
Matt.
---
This SF.Net email is sponsored by: IBM Linux Tutorials
On Wed, 2004-03-17 at 16:57, Matthew Mastracci wrote:
Gert Driesen wrote:
You mean an attribute that didn't exist ? Properties that don't exist cause
a build error already ...
Yep - that's what I was thinking.
But I agree that we should indeed have this mode (or just always run NAnt
I've written a custom task, put the
compiled DLL in the same directory as nant.exe, named it XXXTasks.dll,
and my public class inherits from task and has the TaskNameAttribute.
But when I attempt to use it, I get
the following:
[Core.TypeFactory:Error loading Elements
from
