stylecop

I used previously StyleCop + FxCop on my Visual Studio's projects. But now I am testing Visual Studio Code Analysis tool, which is easier to integrate into MSBuild, and I have found that this tools analyses some of the rules of both FxCop and StyleCop. Is this tool a full replacement for both FxCop and StyleCop or does it just implement some of their rules? Ben S Visual Studio includes FxCop + more. From the developer blog of FxCop : Sorry about my ignorance, but I assume FxCop is completely separate from the Code Analysis in VSTS? More specifically, I assume that if I install the new version

I'm using StyleCop and want to suppress some warning which does not suit my style. I prefer to have solution for 1) in-line code suppressing 2) global setting suppressing I've searched the internet but still not sure how to do the suppressing. For method 1), They said to add the lines: [assembly: SuppressMessage("Microsoft.Design", "SA1202:All private methods must be placed after all public methods", Scope = "namespace", Target = "Consus.Client.ClientVaultModule.Services.OnlineDetection")] But they do not say where and which namespace to be used. For method 2), they said to use GlobalSuppress

I have been trying to follow StyleCop's guidelines on a project, to see if the resulting code was better in the end. Most rules are reasonable or a matter of opinion on coding standard, but there is one rule which puzzles me, because I haven't seen anyone else recommend it, and because I don't see a clear benefit to it: SA1101: The call to {method or property name} must begin with the 'this.' prefix to indicate that the item is a member of the class. On the downside, the code is clearly more verbose that way, so what are the benefits of following that rule? Does anyone here follow that rule?