It currently doesn't pass CodeAnalysis (and CodeAnalysis is disabled project-wide).
Comments: In order to get this to work as part of the build, two things need to be done: 1. In the portable csproj, the following property needs to be added: <CodeAnalysisAdditionalOptions> /assemblycomparemode:StrongNameIgnoringVersion</CodeAnalysisAdditionalOptions> 2. /searchGac needs to be suppressed from the FxCopCmd command line. Failure to do this results in a StackOverflow exception. We need to figure out how to suppress this at a project level. After manually removing /searchGac from the generated command line, code analysis runs. All standard FxCop rules pass. However two of our custom rules generate exceptions when run on the portable library. This appears to be a bug in our custom rule implementation in regards to portable library compatibility and needs to be addressed before enabling FxCop on the portable library as part of the build. Attached is the analysis log
Comments: In order to get this to work as part of the build, two things need to be done: 1. In the portable csproj, the following property needs to be added: <CodeAnalysisAdditionalOptions> /assemblycomparemode:StrongNameIgnoringVersion</CodeAnalysisAdditionalOptions> 2. /searchGac needs to be suppressed from the FxCopCmd command line. Failure to do this results in a StackOverflow exception. We need to figure out how to suppress this at a project level. After manually removing /searchGac from the generated command line, code analysis runs. All standard FxCop rules pass. However two of our custom rules generate exceptions when run on the portable library. This appears to be a bug in our custom rule implementation in regards to portable library compatibility and needs to be addressed before enabling FxCop on the portable library as part of the build. Attached is the analysis log