ccode analysisfxcopvisual-studio-2013
I want to do code analysis in my project and I am using Visual Studio 2013. I can see a Analyze tab which will help to do the code analysis. So my questions is below
Just found a post here, but I am not sure whether to use Fxcop or not?
http://michaelsync.net/2014/07/19/status-of-fxcop-code-analysis
Possible solutions:
devenv /SafeModeStarts Visual Studio in safe mode, loading only the default environment and services.
devenv /setupForces Visual Studio to merge the resource metadata that describes menus, toolbars, and command groups, from all available VSPackages.
devenv /ResetSettingsRestores the default settings for Visual Studio and automatically launches its integrated development environment (IDE). Optionally resets the settings to the specified .vssettings file.
devenv /ResetSkipPkgsClears all options to skip loading added to VSPackages by users wishing to avoid loading problem VSPackages, then starts Visual Studio.
VS Code Analysis includes some rules that are not included with stand-alone FxCop. You will need to ensure that the extra rule assemblies are available to fxcopcmd.exe. The easiest way to do this is to replace the contents of your build-source FxCop folder with those from your Visual Studio installation since one of the rule assemblies (DataflowRules.dll) uses an analysis engine that isn't included with stand-alone FxCop either, and that depends on a bunch of other assemblies that are also included in the FxCop folder under the VS installation folder hierarchy.
Best Answer
(Disclaimer: I worked on Visual Studio at Microsoft, though not on the C# or CIL/FxCop teams and I have no inside knowledge of their work)
My understanding is that the Code Analysis engine in Visual Studio 2013 (under the Analyze menu) is essentially the same engine as used in FxCop, except built-in to Visual Studio and MSBuild (which makes build analysis easier to automate). VS2013 uses the old "hand-written" native C# and VB.NET compilers.
Visual Studio 2015 ("VS 14") uses the new "Roslyn" compiler set and its analysis engine is different. The blog article you linked to makes this clear:
...from that, it's said that VS2015 includes the old FxCop rules in addition to new Roslyn-based rules, but the less reliable FxCop CIL-based rules have been replaced with Roslyn rules.