«

Hi

I am currently having problems with Validators in a user control. I am
creating a wizard sign-up process which have the allocated step
(hyperlinks" at the top of the page. A user can also click
next/previous. Dependant on the current step in the sign-up process I
am loading a new user control as I dont want to have 7-8 pages, just
one page and load the control dynamically.

All is sweet at the moment apart from the validation controls that are
assigned to each user control. Any link that is clicked or button that
is clicked should cause validation on that user control, however I have
performed the following (from another thread)

1. Set EnableClientScript=false on each validator.
2. Set CausesValidation=false on each button that submits the page.
This
prevents the Page.Validate() method from begin called automatically by
the
button.
3. In your click event method, you will call the Validate() method on
each
validator that is associated with the submit button. Then you will test
the
IsValid property to be true on each validator before saving.

I am performing this process BUT as I loop on each validate control
with the allocated user control the isValid IS ALWAYS true. I am sure
its something to do with not loading something or just a simple step I
have missed.. I would appreciate any help on this, some code:

private bool Persist() {
//first check whether we have valid data
AddStockCommon ctrl =
(AddStockCommon)this.FindControl(String.Format("{0 }{1}",
ViewState["Context"], ".ascx"));

foreach(Control ct in ctrl.Controls) {
if (ct is BaseValidator) {
BaseValidator validator = (BaseValidator)ct;
validator.Validate();

if (!validator.IsValid) {
return false;
}
}

return true;
}


Many thanks

Richard

OK

To anyone out there..... Further investigations yielded no solutions
until I decided to make the validators visible (They were set invisible
as I wanted a summary to appear only).

Setting them Visible suddenly made the client side validators work on
the browser, but I have to say that this looks clunky and totally
unusable, (mabe my designer could do something )

I am now going to do my own checks on the server upon a post back, as
this will say me time understanding these validators which to all
intents and purposes seem like a last minute thought to .NET 1.1.

I hope they have improved on .NET 2.0, and if anyone can either point
me in the right direction then I'll maybe return to this validation
technique but for now its easier (on the eye and technically) to
perform all validation server side...

If anyone can tell me why setting these validators Invisible affects
how they work then I would be glad to hear.

Many thanks

Richard

Check out the image in this article. They talk about the same thing,
that the validation summary is ugly.

http://www.codeproject.com/aspnet/vsum.asp

There may be a solution here as well
http://www.asp101.com/articles/manu/...ry/default.asp

jp


wrote:
> OK
>
> To anyone out there..... Further investigations yielded no solutions
> until I decided to make the validators visible (They were set invisible
> as I wanted a summary to appear only).
>
> Setting them Visible suddenly made the client side validators work on
> the browser, but I have to say that this looks clunky and totally
> unusable, (mabe my designer could do something )
>
> I am now going to do my own checks on the server upon a post back, as
> this will say me time understanding these validators which to all
> intents and purposes seem like a last minute thought to .NET 1.1.
>
> I hope they have improved on .NET 2.0, and if anyone can either point
> me in the right direction then I'll maybe return to this validation
> technique but for now its easier (on the eye and technically) to
> perform all validation server side...
>
> If anyone can tell me why setting these validators Invisible affects
> how they work then I would be glad to hear.
>
> Many thanks
>
> Richard

By definition, when any web control has Visible=false, that turns off the
control. It will not generate anything to the client-side. It isn't a style
that shows and hide things. (Besides the validators have the job of showing
and hiding themselves.) Since the validator is off when Visible=false, the
call to Validator.Validate() or even Page.Validate() will do nothing to the
validator.

Recommendation: Use Validation Groups, one for each page. This comes with
ASP.NET 2.0 and my Professional Validation And More
(http://www.peterblum.com/vam/home.aspx) which works with all versions of
ASP.NET.

>>> Setting them Visible suddenly made the client side validators work on
>>> the browser, but I have to say that this looks clunky and totally
>>> unusable, (mabe my designer could do something )

If you set EnableClientScript=false on each validator, there should be no
client-side validation. Confirm these settings.
What does "looks clunky" mean? One guess is that validators are changing
their spacing on the screen, moving things around. Use
Validator.Display=Static or set the Text property to "*" and add a
ValidationSummary to show the actual error.

--- Peter Blum
www.PeterBlum.com
Email:
Creator of "Professional Validation And More" at
http://www.peterblum.com/vam/home.aspx

<> wrote in message
news: oups.com...
> Hi
>
> I am currently having problems with Validators in a user control. I am
> creating a wizard sign-up process which have the allocated step
> (hyperlinks" at the top of the page. A user can also click
> next/previous. Dependant on the current step in the sign-up process I
> am loading a new user control as I dont want to have 7-8 pages, just
> one page and load the control dynamically.
>
> All is sweet at the moment apart from the validation controls that are
> assigned to each user control. Any link that is clicked or button that
> is clicked should cause validation on that user control, however I have
> performed the following (from another thread)
>
> 1. Set EnableClientScript=false on each validator.
> 2. Set CausesValidation=false on each button that submits the page.
> This
> prevents the Page.Validate() method from begin called automatically by
> the
> button.
> 3. In your click event method, you will call the Validate() method on
> each
> validator that is associated with the submit button. Then you will test
> the
> IsValid property to be true on each validator before saving.
>
> I am performing this process BUT as I loop on each validate control
> with the allocated user control the isValid IS ALWAYS true. I am sure
> its something to do with not loading something or just a simple step I
> have missed.. I would appreciate any help on this, some code:
>
> private bool Persist() {
> //first check whether we have valid data
> AddStockCommon ctrl =
> (AddStockCommon)this.FindControl(String.Format("{0 }{1}",
> ViewState["Context"], ".ascx"));
>
> foreach(Control ct in ctrl.Controls) {
> if (ct is BaseValidator) {
> BaseValidator validator = (BaseValidator)ct;
> validator.Validate();
>
> if (!validator.IsValid) {
> return false;
> }
> }
>
> return true;
> }
>
>
> Many thanks
>
> Richard
>