I want to try to convert a string to a Guid, but I don't want to rely on catching exceptions (
- for performance reasons - exceptions are expensive
- for usability reasons - the debugger pops up
- for design reasons - the expected is not exceptional
In other words the code:
public static Boolean TryStrToGuid(String s, out Guid value)
{
try
{
value = new Guid(s);
return true;
}
catch (FormatException)
{
value = Guid.Empty;
return false;
}
}
is not suitable.
I would try using RegEx, but since the guid can be parenthesis wrapped, brace wrapped, none wrapped, makes it hard.
Additionally, I thought certain Guid values are invalid(?)
Update 1
ChristianK had a good idea to catch only FormatException
, rather than all. Changed the question's code sample to include suggestion.
Update 2
Why worry about thrown exceptions? Am I really expecting invalid GUIDs all that often?
The answer is yes. That is why I am using TryStrToGuid - I am expecting bad data.
Example 1 Namespace extensions can be specified by appending a GUID to a folder name. I might be parsing folder names, checking to see if the text after the final . is a GUID.
c:\Program Files
c:\Program Files.old
c:\Users
c:\Users.old
c:\UserManager.{CE7F5AA5-6832-43FE-BAE1-80D14CD8F666}
c:\Windows
c:\Windows.old
Example 2 I might be running a heavily used web-server wants to check the validity of some posted back data. I don't want invalid data tying up resources 2-3 orders of magnitude higher than it needs to be.
Example 3 I might be parsing a search expression entered by a user.
If they enter GUID's I want to process them specially (such as specifically searching for that object, or highlight and format that specific search term in the response text.)
Update 3 - Performance benchmarks
Test converting 10,000 good Guids, and 10,000 bad Guids.
Catch FormatException:
10,000 good: 63,668 ticks
10,000 bad: 6,435,609 ticks
Regex Pre-Screen with try-catch:
10,000 good: 637,633 ticks
10,000 bad: 717,894 ticks
COM Interop CLSIDFromString
10,000 good: 126,120 ticks
10,000 bad: 23,134 ticks
p.s. I shouldn't have to justify a question.
4.0
. That's why the question, and accepted answer, are the way they are. – Ian Boyd