New Post: CA1709 Code Analysis Errors

@MichaelPoettge Given that the build works for the majority of people it would be good to determine what is different about your environment that is causing it to fail on your machine before adding suppressions that do not seem to be needed. If the root cause turns out to be that the suppressions are needed and that it works for most people without them due to some error in the build, FxCop, or whatever, then we will add the suppressions. But I would like to understand the root cause first. In the past we have seen this issue when there are multiple versions of Visual Studio installed on the same machine. It seems that sometimes some older FxCop files get used instead of the VS 2012 files in some situations. This is why I asked which versions of Visual Studio you have installed on the machine. Also, in the past build worked fine even when multiple versions of VS are installed on the machine so long as the "VS2012 x86 Native Tools Command Prompt". So if you have a machine where the build doesn't work even when using that command prompt then knowing which versions of VS are on the box seems like a good starting point for attempting to root cause this. If you have other ideas of how to reproduce it then that would also be good.

Thanks,
Arthur