Should FxCop "indicate iformat provider" to catch Int32.TryParse violations?

Question

The FxCop Globalization Rule, "Specify an IFormat Provider," does not block Int32.TryParse violations for me. Is this a mistake, or am I doing something wrong?

Answer 1

Most likely, because Int32.TryParse without additional parameters will refuse to parse strings containing group separators or decimal separators:

Int32.TryParse("1.234", out temp);  // => false
Int32.TryParse("1,234", out temp);  // => false
Int32.TryParse("1234", out temp);   // => true, temp = 1234

Thus, Int32.TryParse is probably not considered culture sensitive with FxCop.