Our DEV team has been using FB for the last 3 years without any major issues. About a year ago or so, we decided to enable code analysis on some of our legacy C# projects and dump all of the existing issues into the standard GlobalSuppressions.cs file. When doing a complete end-to-end build using Final Builder7, the first time you fire up any of our solutions and build from within Visual Studio results in code analysis failures. For some odd reason, all of the suppressions contained in those GlobalSuppressions.cs file are ignored.
Once the initial failure occurs, developers have been conditioned to doing a Clean->Rebuild and the build completes successfully. If we repeat this entire exercise doing an end-to-end building only through a Visual Studio solution, however, this problem never occurs. Since Visual Studio uses MSBUILD, it would seem that Visual Studio might be doing something different than FB7 in terms of the command line parameters? We have lived with this quirk for as long as we have been using code analysis but figured it was time to see if a workaround exists.
Our DEV environment includes VS 2010 SP1 and FB7 v7.0.0.716. I should also mention that this problem has existed for as long as we have been using FB (starting with FB6).