on't need.
Ian
>-Original Message-
>From: Ian MacLean [mailto:[EMAIL PROTECTED]]
>Sent: Monday, September 30, 2002 2:20 PM
>To: Scott Hernandez
>Cc: 'Barkley, Chris'; [EMAIL PROTECTED]
>Subject: Re: [nant-dev] Adding Validators
>
>
>I think some of this came out
: 'Barkley, Chris'; [EMAIL PROTECTED]
Subject: Re: [nant-dev] Adding Validators
I think some of this came out when InitializeAttributes was originally
rewritten. As it stands we only have BooleanValidator and
Int32Validator. In fact this line of code
paramaters[0] = Convert.ChangeType
I think some of this came out when InitializeAttributes was originally
rewritten. As it stands we only have BooleanValidator and
Int32Validator. In fact this line of code
paramaters[0] = Convert.ChangeType(attrValue, propertyInfo.PropertyType);
will throw an exception if attrValue cannont safe
2 PM
> To: Shaw, Gerry
> Subject: RE: [nant-dev] Adding Validators
>
>
> Gerry,
> The final verdict after hours of debugging I have found that
> the Validators are never called. I have put breakpoints in
> all of them and ran scripts that contained tasks that had all
>
I would call this feature missing a bug. It seems like we need to add
some unit tests to check this so more features don't disappear.
I looked in an old snapshot of nant (circa may 17th) and there is
validation related code commented out there. It must have been removed
from the file sometime aft
Message-
From: Shaw, Gerry [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 25, 2002 8:49 PM
To: Barkley, Chris; [EMAIL PROTECTED]
Subject: RE: [nant-dev] Adding Validators
> Do I need to update
> any files to tell it that this new validator?
To be honest Chris I don't know
> Do I need to update
> any files to tell it that this new validator?
To be honest Chris I don't know. I suggest you set a breakpoint on the
BooleanValidator code and trace through it. I believe the code is in
the Element.cs that will be of interest.
Feel free to comment the BuildAttributeAtt
I recently tried to add a new Validator but can not get it to work. I copied
the BooleanValidator to HKeyValidator and modified it to return an error
every time no matter what the value entered. I then add the [HKeyValidator]
to an attribute in a task. When I run the build script that calls thi
