I've read a bit about the CA1709 and how to avoid it. Having read that I do believe that FxCop is right about flagging this as an error, because there are no casing exceptions defined for the acronyms in the code analysis dictionary. What I can't get my head around to is why this should cause problems on one machine but not on another. Two things I came up with comparing my machine with my colleague's machine: different editions of Visual Studio (Premium vs. Professional) and different OS languages (German vs. English). Not sure if any of that has an influence on FxCop. The FxCop versions appeared to be the same.
To solve the problem one just has to extend the src\CodeAnalysisDictionary.xml to include a Dictionary/Acronyms element like so:
To solve the problem one just has to extend the src\CodeAnalysisDictionary.xml to include a Dictionary/Acronyms element like so:
<Dictionary>
<Words>
...
</Words>
<Acronyms>
<CasingExceptions>
<Acronym>Db</Acronym>
<Acronym>Ce</Acronym>
</CasingExceptions>
</Acronyms>
</Dictionary>