regex guid tester

[Greg Merideth]

I came up with this to test strings passed into a checking method to see
if the guid being passed in (regular 128 bit windows registry GUID) is
valid.

So far it seems to handle most errors thrown at it but today during a
test, a bracket "}" passed through the method as a valid guid so I
wanted to know if this expresion will stop invalid guids or did I miss
something?

__systemGUID is the string passed in.

if(!Regex.IsMat ch(__systemGUID ,
@"^([\w]{8}-[\w]{4}-[\w]{4}-[\w]{4}-[\w]{12})"))

Thanks.

[Larry Brasfield]

"Greg Merideth" <be*****@forwar dtechnology.net > wrote in message
news:j8******** ************@co mcast.com...

I came up with this to test strings passed into a checking method to see if the guid being passed in (regular 128 bit windows
registry GUID) is valid.

So far it seems to handle most errors thrown at it but today during a test, a bracket "}" passed through the method as a valid
guid so I wanted to know if this expresion will stop invalid guids or did I miss something?

__systemGUID is the string passed in.

if(!Regex.IsMat ch(__systemGUID , @"^([\w]{8}-[\w]{4}-[\w]{4}-[\w]{4}-[\w]{12})"))
The non-dash stuff should be hexadecimal, not any old
alphanumeric character.
Thanks.

--
--Larry Brasfield
email: do************* **********@hotm ail.com
Above views may belong only to me.

[Chris R. Timmons]

Greg Merideth <be*****@forwar dtechnology.net > wrote in
news:j8******** ************@co mcast.com:

I came up with this to test strings passed into a checking
method to see if the guid being passed in (regular 128 bit
windows registry GUID) is valid.

So far it seems to handle most errors thrown at it but today
during a test, a bracket "}" passed through the method as a
valid guid so I wanted to know if this expresion will stop
invalid guids or did I miss something?

__systemGUID is the string passed in.

if(!Regex.IsMat ch(__systemGUID ,
@"^([\w]{8}-[\w]{4}-[\w]{4}-[\w]{4}-[\w]{12})"))

Thanks.

Greg,

To expand on Larry's answer, \w matches way too many different
characters. Your regex matches strings like this:

xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Instead of \w, a character class of [\dA-Fa-f] should be used:

^([\dA-Fa-f]{8}-[\dA-Fa-f]{4}-[\dA-Fa-f]{4}-[\dA-Fa-f]{4}-[\dA-Fa-f]{12})

--
Hope this helps.

Chris.
-------------
C.R. Timmons Consulting, Inc.
http://www.crtimmonsinc.com/

[Joakim Karlsson]

The following also takes into account curly braces in a guid, and it
contains a end of line marker ($).

^\{?[\dA-Fa-f]{8}-[\dA-Fa-f]{4}-[\dA-Fa-f]{4}-[\dA-Fa-f]{4}-[\dA-Fa-f]{12}\}?$

Without the end-of line, the following would slip through:
CEEBB5B7-5AB7-4605-B5B3-39D8A9511517NOT _VALID!!!!

Regards,
Joakim

Chris R. Timmons wrote:

Greg Merideth <be*****@forwar dtechnology.net > wrote in
news:j8******** ************@co mcast.com:

I came up with this to test strings passed into a checking
method to see if the guid being passed in (regular 128 bit
windows registry GUID) is valid.

So far it seems to handle most errors thrown at it but today
during a test, a bracket "}" passed through the method as a
valid guid so I wanted to know if this expresion will stop
invalid guids or did I miss something?

__systemGUI D is the string passed in.

if(!Regex.IsM atch(__systemGU ID,
@"^([\w]{8}-[\w]{4}-[\w]{4}-[\w]{4}-[\w]{12})"))

Thanks.

Greg,

To expand on Larry's answer, \w matches way too many different
characters. Your regex matches strings like this:

xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Instead of \w, a character class of [\dA-Fa-f] should be used:

^([\dA-Fa-f]{8}-[\dA-Fa-f]{4}-[\dA-Fa-f]{4}-[\dA-Fa-f]{4}-[\dA-Fa-f]{12})

[Greg Merideth]

Ahh that damm "$" is what I forgot to add to the regex check. Must be
old age.

Thanks.

Joakim Karlsson wrote:

The following also takes into account curly braces in a guid, and it
contains a end of line marker ($).

^\{?[\dA-Fa-f]{8}-[\dA-Fa-f]{4}-[\dA-Fa-f]{4}-[\dA-Fa-f]{4}-[\dA-Fa-f]{12}\}?$
Without the end-of line, the following would slip through:
CEEBB5B7-5AB7-4605-B5B3-39D8A9511517NOT _VALID!!!!

Regards,
Joakim

Chris R. Timmons wrote:

Greg Merideth <be*****@forwar dtechnology.net > wrote in
news:j8******** ************@co mcast.com:

I came up with this to test strings passed into a checking
method to see if the guid being passed in (regular 128 bit
windows registry GUID) is valid.

So far it seems to handle most errors thrown at it but today
during a test, a bracket "}" passed through the method as a
valid guid so I wanted to know if this expresion will stop
invalid guids or did I miss something?

__systemGUID is the string passed in.

if(!Regex.IsMat ch(__systemGUID ,
@"^([\w]{8}-[\w]{4}-[\w]{4}-[\w]{4}-[\w]{12})"))

Thanks.

Greg,

To expand on Larry's answer, \w matches way too many different
characters. Your regex matches strings like this:

xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Instead of \w, a character class of [\dA-Fa-f] should be used:

^([\dA-Fa-f]{8}-[\dA-Fa-f]{4}-[\dA-Fa-f]{4}-[\dA-Fa-f]{4}-[\dA-Fa-f]{12})