facebook-csharp-sdk/facebook-csharp-sdk — pull request #111 by PaulECoyote (2012-03-04 05:23:53+00:00)
Title: Supressed warning spam.  Obsolete messages RE: ApiAsync most iffy, other...

Compiling with source, there are way to many warnings to work with the Sdk as a dependency project.
So I suppressed the warning spam in the 4.0 project. Obsolete messages RE: ApiAsync most iffy and close to "real" warnings, others are just xml document warnings and code analysis disagreeing with your design choices.

There are two files I used pragma disable in for the obsolete messages, though using the TODO: marker so at least they will appear in Visual Studio's task list.

I suggest a warnings pass when enabling the code analysis rules *then* submitting it with either the warnings fixed or the rules suppressed where necessary.

I personally treat warnings more like errors... so find it pretty difficult to work with all those yellow lights there. Especially when working with my own code.

I realise you may not agree with any of the above - but consider the impression you leave with a developer who just started to look at the project and how alarming over a hundred warnings might be.