All --

Please help.

How can one use the CompareValidator for case-insensitive string validation?

Please advise.

I see this property...

ViewStateIgnoresCase

...here...

http://msdn.microsoft.com/en-us/library/system.web.ui.control.viewstateignorescase.aspx 

...which may help-- but, I am not sure if it will work or if it is a good way to do it.

I see that some have worked it out with custom code, like this...

StringCompareValidator - Provides Case Sensitive Comparisons

http://dotnetfreak.co.uk/blog/archive/2004/10/30/new-control-stringcomparevalidator-provides-case-sensitive-comparisons.aspx 

...which may help-- but, I am not sure if it will work or if it is a good way to do it.

So, I am still looking for ideas.

What do you think?

Please advise.

Thank you.

-- Mark Kamoski

nobody likes to come here to click on links to try to help you.....

but without looking at either of those links if you want to just do ignore case just do it on your own custom code

 string first= "caca";

string second= "PPOOOPERS";

if (!first.tolower.equals(second.tolower))

lblmyErrors.text="caca != ppooopers try again!";

break;

The ViewStateIgnoresCase property is not related to validation.

The CompareValidator does not support what you request. It always does a case sensitive test with Type=String. (My replacement to the ASP.NET Validators, Peter's Professional Validation, resolves this by offering "String-Case Insensitive" as an option on its own DataType property.)

To solve this, you will have to use a customvalidator because everytime the existing validators don't match your requirements, you use a CustomValidator.

PLBlum:

The ViewStateIgnoresCase property is not related to validation.

The CompareValidator does not support what you request. It always does a case sensitive test with Type=String. (My replacement to the ASP.NET Validators, Peter's Professional Validation, resolves this by offering "String-Case Insensitive" as an option on its own DataType property.)

To solve this, you will have to use a customvalidator because everytime the existing validators don't match your requirements, you use a CustomValidator.

Peter --

I appreciate the excellent reply.

That's pretty much what I thought and I just needed a guru to confirm it.

Thank you.

-- Mark Kamoski