I did perform such a comparison, as part of my job.
I was asked to write coding style guidelines for a software engineering department. As this department was part of the military-industrial complex, the document I wrote was very detailed, and included parts of all of the documents you linked, as well as vast swaths of the Design Guidelines for Developing Class Libraries.
After I submitted my guidelines, I was asked to distill them down to 3 to 4 pages, and then to one crib sheet. In the end, the guidelines were not adopted. Instead, everyone in the department follows the rules encoded into Visual Studio.
Here is what I learned from the experience:
- The coding style to adopt is the one your shop already uses, unless they decide to adopt a new one.
- The guidelines for creating software libraries are already very well defined, and almost universally agreed upon by all, including the authors of the documents you linked.
- The only real variations you are going to see in coding style that are not already universally agreed on are those variations having to do with member variables inside classes (which Microsoft has left up to the taste of individual developers).
- The vast majority of the rules you need to know to develop a good coding style are already encoded in Visual Studio, FxCop, and other Code Analysis tools Microsoft provides.