Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Permalink
main
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Go to file
 
 
Cannot retrieve contributors at this time
title description ms.custom ms.date ms.topic ms.assetid author ms.author manager ms.technology ms.workload
Getting Started with Roslyn Analyzers | Microsoft Docs
Use these resources to get started with Roslyn analyzers in Visual Studio; includes a tutorial and several examples.
SEO-VS-2020
04/02/2018
conceptual
367c2ec8-3059-46a5-9d1c-57bead0419e7
leslierichardson95
lerich
jmartens
vs-ide-sdk
vssdk

Get started with Roslyn analyzers

[!INCLUDE Visual Studio]

With live, project-based code analyzers in Visual Studio, API authors can ship domain-specific code analysis as part of their NuGet packages. Because these analyzers are powered by the .NET Compiler Platform (code-named "Roslyn"), they can produce warnings in your code as you type even before you've finished the line (no more waiting to build your code to discover issues). Analyzers can also surface an automatic code fix through the Visual Studio light bulb prompt to let you clean up your code immediately.

Get started

Roslyn analyzers overview

Tutorial: Write your first analyzer and code fix

Add code fixes Walkthrough: Provide users fixes for analyzer issues

Real world Roslyn analyzer

Several examples on GitHub, grouped into three kinds of analyzers

See also