Anything else you would like to tell the tool (additional libraries locations…). You can download the Web Essentials for Visual Studio 2010 here. NET 5.0, these analyzers are included with the. A new extension CSSCop which is a FXCop for style sheets. NET 5.0, these analyzers shipped as NuGet package. Go through the installation, which is about as standard as they come. Many of the legacy analysis (FxCop) rules have already been rewritten as source analyzers. Make sure you close down any open Visual Studio instances before starting the installer. If left empty, default location (\Rules) is used. You can download FxCop v1.36, which is the latest version as of this writing, here. Specifies a location for FxCop Rules files. Run the restore and build command: build.cmd (in the command prompt) or. c:program filesmicrosoft visual studio 10.0team toolsstatic analysis toolsfxcop c:program files (x86)microsoft visual studio2017communityteam. Specifies the location of the tool the extension is running. Open a command prompt and go to the directory of the Roslyn Analyzer Repo.
Tool can be configured through Tools -> Options -> FxCop Runner.įxCopCmd.exe file location: Necessary.
When tool is invoked, the following happens:Īll changes made to source files are saved.įxCopCmd tool is run, its output is parsed and error list is filled. This Visual Studio extension integrates FxCop into Visual Studio more nicely. Microsoft tool FxCop is available for download for free, but its integration with Visual Studio is nonexistent (save the external tool, where you are limited to looking at the output).
Microsoft Visual Studio 2010 Professional does not come with a code analysis tool.