ASP.NET Regular Expression Validator not validating as expected

Question

I am trying to validate a phone number in the format (###)###-#### with $[0-9]{3}$[0-9]{3}-[0-9]{4} in visual studio using the regular expression validator. I am receiving the error message with (111)111-1111. Yet when I do this on a regex testing site it works fine. Is there something else at play here that I am missing?

<asp:RegularExpressionValidator
     ID="PhoneValidator"
     runat="server"
     ErrorMessage="Phone Format Must Be (###)###-####" 
     ValidationExpression="/\([0-9]{3}\)[0-9]{3}-[0-9]{4}/g"
     Display="None" 
     ControlToValidate="PhoneTextBox">
</asp:RegularExpressionValidator>

Which site? Different regex engines have subtle differences. — neontapir
– neontapir, Commented Oct 21, 2013 at 18:58
I also notice that in your validator, you are using /pattern/g, which appears to be interpreted as part of the pattern instead of as a regex directive. — neontapir
– neontapir, Commented Oct 21, 2013 at 19:01

Bobson · Accepted Answer · 2013-10-21 19:01:28Z

5

If you look at the example here, you'll see that in this context the regular expression should not start and end with / markers. Try this instead:

ValidationExpression="^\([0-9]{3}\)[0-9]{3}-[0-9]{4}$"

The ^ and $ ensure you're not accepting extra characters before or after the phone number.

answered Oct 21, 2013 at 19:01

Bobson

13.7k5 gold badges59 silver badges85 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Win · Accepted Answer · 2013-10-21 19:16:58Z

1

You also want to consider extension too. For example, (770)123-4567 x1234.

((\(\d{3}\) ?)|(\d{3}-))?\d{3}-\d{4}( x\d{0,})?

Validating Phone Numbers with Extensions in ASP.NET

answered Oct 21, 2013 at 19:16

Win

62.4k13 gold badges106 silver badges190 bronze badges

Comments

Burning Hippo · Accepted Answer · 2013-10-21 20:09:32Z

0

I was actually having a problem elsewhere on the page sending a blank textbox of a date. Apparently C# interpreted the empty field as 01/01/0001 and therefore made it out of range. This was throwing everything else off. @neontapir You are right; I should not have had those on the expression. I didn't originally but just so happens I did when I posted this. Thanks.

answered Oct 21, 2013 at 20:09

Burning Hippo

8052 gold badges22 silver badges47 bronze badges

Collectives™ on Stack Overflow

ASP.NET Regular Expression Validator not validating as expected

3 Answers 3

Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related