Sorting it all Out Michael Kaplan's random stuff of dubious value Be sure to read the disclaimer here first!
Scott figured it out, and it was not a Microsoft bug.:-)
You can read about the details on Scott's blog at Update on the dasBlog Turkish-I bug and a reminder to me on Globalization.
Now I have talked about the Turkish I issue in general before (cf: The [Upper]Case of the Turkish İ (or: Casing, the 2nd)), but I will post some more on this soon. But Scott's object lesson here is even cooler -- you can see how easy it is for internationalization issues can bite you if you are not very careful....
Thought FWIW -- Scott, do not feel too bad. Microsoft has had to fix many such bugs in the past. One of the biggest reasons for Microsoft to produce documents like the New String Recommendations is because even internally people were having problems, and MS wanted to have some solid guidelines to help people avoid those issues (and thus not have bugs!).
It is a tester's dream -- they can always find issues in an area like this!
If you are someone who reads the BCL Team blog, you may have seen Josh Free's String.Compare() != String.Equals()
JJ's question was simple enough: Hello, This is probably not the right alias for this, but... I have