Sometimes FxCop Is Ahead Of The Framework
Today at work, two of us on my team were presented with a violation of FxCop rule CA1300. The violation, in this case, discusses using an overload of the MessageBox.Show method that does not specify the reading direction (i.e. right to left or not). The recommendation for fixing the violation is to search the parent forms until you find one that has the reading direction specified and use that.
Maybe it’s just me, but that seems like something that could be done by a computer.
Write a comment