{"id":23818,"date":"2019-07-10T09:40:11","date_gmt":"2019-07-10T16:40:11","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/dotnet\/?p=23818"},"modified":"2019-07-10T09:38:21","modified_gmt":"2019-07-10T16:38:21","slug":"write-better-code-faster-with-roslyn-analyzers","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/write-better-code-faster-with-roslyn-analyzers\/","title":{"rendered":"Write Better Code Faster with Roslyn Analyzers"},"content":{"rendered":"

Roslyn, the .NET compiler platform, helps you catch bugs even before you run your code. One example is Roslyn\u2019s spellcheck analyzer that is built into Visual Studio. Let\u2019s say you are creating a static method and misspelled the word static<\/em> as statc<\/em>. You will be able to see this spelling error before you run your code because Roslyn can produce warnings in your code as you type even before you\u2019ve finished the line. In other words, you don\u2019t have to build your code to find out that you made a mistake.<\/p>\n

\"Roslyn<\/p>\n

Roslyn analyzers can also surface an automatic code fix through the Visual Studio light bulb icon that allows you to fix your code immediately.<\/p>\n

But what if you could catch even more bugs?<\/strong><\/span><\/p>\n

Let me introduce you to Roslyn analyzer packages. These collections of analyzers provide a more verbose analysis, but don’t ship with the default Visual Studio tools. To learn more about our favorite Roslyn analyzers visit our Roslyn analyzers GitHub repository<\/a>. This repository includes the FxCop rules that are still applicable to modern software development, but now target our modern code analysis platform based on Roslyn. Let’s go ahead and install this package to be more productive and write better code faster!<\/p>\n

To Install FxCop analyzers as a NuGet package:<\/p>\n

    \n
  1. Assuming you\u2019re using Visual Studio 2017 Version 15.8 or newer, choose the most recent version of Microsoft.CodeAnalysis.FxCopAnalyzers<\/a>.<\/li>\n
  2. Install the package in Visual Studio, using the Package Manager UI<\/a>.<\/li>\n<\/ol>\n

    \"Roslyn<\/p>\n

    Once you have the package installed you can simply customize the analyzer diagnostics from the Solution Explorer. An analyzer node will appear under the References or Dependencies node in the Solution Explorer. If you expand the analyzers, and then expand one of the analyzer assemblies, you can see all the diagnostics in the assembly.<\/p>\n

    \"Roslyn<\/p>\n

    You can view the properties of a diagnostic, including its description and default severity, in the properties window. To view the properties, right-click on the rule and select\u00a0Properties<\/strong>, or select the rule and then press\u00a0Alt<\/strong>+Enter<\/strong>.<\/p>\n

    \"Roslyn<\/p>\n

    The icons next to each diagnostic in\u00a0Solution Explorer\u00a0correspond to the icons you see in the rule set when you open it in the editor:<\/p>\n