Occasionally when I generate a GUID using visual studio, the 14th hex character is lowercase while the rest of the hex digits are uppercase.
Cause a bit of problem when comparing the string representations of two GUIDs. Now I always compare the binary equivalents to be safe.
Yes, this is a known bug. But you shouldn't be making string comparisons; use
Guid.Equals
instead.