I use OrdinalIgnoreCase since we use only the ASCII characters :) At the point of the suspected code both string *should* be semantically equal. I added the comparison only for guarding reasons. Once in a while it encounters a difference ...
// Ryan On Mon, Sep 8, 2008 at 7:23 PM, Sébastien Lorion <[EMAIL PROTECTED]> wrote: > What is the result if you use CurrentCultureIgnoreCase or > InvariantCultureIgnoreCase? Also, by using OrdinalIgnoreCase, you are > limiting yourself to only the first 128 chars of ASCII, which in 2008 is > kinda out of fashion... > > Sébastien > On Mon, Sep 8, 2008 at 7:25 AM, Ryan Heath <[EMAIL PROTECTED]> wrote: > >> On Mon, Sep 8, 2008 at 1:04 PM, Simon Robinson <[EMAIL PROTECTED]> >> wrote: >> >> > 1. Check the culture settings that your code is working in. I think that >> > override of String.Compare() is culture-dependant, so maybe there's some >> > unusual culture that doesn't recognize eg. 'r' and 'R' as being >> equivalent? >> >> I believe StringComparison.OrdinalIgnoreCase is culture independent >> (when it can)? >> >> > 2. Check the actual unicode values of the characters in your strings. Is >> > it possible that the 'r' (taking one random character as an example) >> > actually isn't an 'r' but is some other unusual unicode character that >> > just happens to look like an 'r' when displayed in your default font? >> >> I'll log the unicode values of the strings too, lets see what that >> will bring up. >> >> // Ryan >> >> =================================== >> This list is hosted by DevelopMentor(R) http://www.develop.com >> >> View archives and manage your subscription(s) at >> http://discuss.develop.com >> > > =================================== > This list is hosted by DevelopMentor(R) http://www.develop.com > > View archives and manage your subscription(s) at http://discuss.develop.com > =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
