Commented Issue: Build.cmd uses VS2010 for code analysis if both VS2012 and VS2010 are installed. [899]

This causes some unexpected FxCop errors to be generated--see this discussion: http://entityframework.codeplex.com/discussions/434294#post1005879

I took a quick look and it's not clear why this is happening--it may be a bug in MSBuild or similar. A quick fix is to add suppressions for the FxCop errors as mentioned in the discussion thread, but a deeper fix would be better if feasible.
Comments: Running from a Visual Studio 2012 x86 Native Tools command prompt causes the build to succeed (I was running from just plain cmd - command prompt)