No description, website, or topics provided.
Clone or download
dotpaul Merge pull request #1991 from LingxiaChen/master
 Implement the Semmel rule CertificateValidationDisabled.ql into Roslyn
Latest commit 8fe2bf2 Jan 21, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Update ISSUE_TEMPLATE.md Sep 25, 2018
assets Move EULA to assets dir Jun 13, 2017
docs Merge pull request #2010 from mavasani/SingleLetterTypeParams Jan 15, 2019
eng Move to latest analyzers NuGet package Jan 17, 2019
nuget Delete Microsoft.Net.RoslynDiagnostics and Unfactored analyzers Jan 10, 2019
src Merge branch 'master' of https://github.com/LingxiaChen/roslyn-analyzers Jan 21, 2019
tools Update to RT 1.0.0-beta2-62922-02 May 22, 2018
.editorconfig Dogfood .editorconfig based configuration for FxCop analyzers Jan 17, 2019
.gitattributes Update to RT 1.0.0-beta2-62922-02 May 22, 2018
.gitignore Update to RT 1.0.0-beta2-62922-02 May 22, 2018
.vsts-ci.yml Migrate to Arcade Sep 24, 2018
Build.cmd Migrate to Arcade Sep 24, 2018
CopyrightHeader.md Modify copyright header template Feb 12, 2016
Directory.Build.props Dogfood .editorconfig based configuration for FxCop analyzers Jan 17, 2019
Directory.Build.targets Migrate to Arcade Sep 24, 2018
License.txt Modify copyright header template Feb 12, 2016
README.md Update README.md Jan 10, 2019
Restore.cmd Migrate to Arcade Sep 24, 2018
RoslynAnalyzers.sln Delete Microsoft.Net.RoslynDiagnostics and Unfactored analyzers Jan 10, 2019
THIRD-PARTY-NOTICES.txt Address feedback + consume an approved version of humanizer Jan 4, 2019
Test.cmd Migrate to Arcade Sep 24, 2018
VERSIONING.md Update VERSIONING.md Jan 10, 2019
codecov.yml Update codecov integration to more closely match the work in RepoToolset Feb 27, 2018
global.json Arcade 18476.3 Sep 26, 2018
netci.groovy Migrate to Arcade Sep 24, 2018
nuget.config Migrate to Arcade Sep 24, 2018

README.md

.NET Compiler Platform ("Roslyn") Analyzers

Join the chat at https://gitter.im/roslyn-analyzers/Lobby

This repository contains a number of Roslyn diagnostic analyzers initially developed to help flesh out the design and implementation of the static analysis APIs. They have been migrated from the main dotnet/roslyn repository in order to continue and speed their further development.

Pre-release builds are available on MyGet gallery: https://dotnet.myget.org/Gallery/roslyn-analyzers.

Windows Debug Windows Release
master Build Status codecov Build Status

Projects

MetaCompilation

Created by summer 2015 interns Zoë Petard, Jessica Petty, and Daniel King

The MetaCompilation Analyzer is an analyzer that functions as a tutorial to teach users how to write an analyzer. It uses diagnostics and code fixes to guide the user through the various steps required to create a simple analyzer. It is designed for a novice analyzer programmer with some previous programming experience.

For instructions on using this tutorial, see Instructions.

Microsoft.CodeAnalysis.Analyzers

Latest stable version: NuGet

Provides guidelines for using .NET Compiler Platform ("Roslyn") APIs.

More info

Microsoft.CodeQuality.Analyzers

Latest stable version: NuGet

Provides common code quality guidelines.

More info

Microsoft.CodeQuality.Analyzers.Exp

Latest pre-release version: NuGet

Experimental package based on Dataflow Analysis to provide code quality guidelines in executable code.

More info

Microsoft.NetCore.Analyzers

Latest stable version: NuGet

Analyzers for APIs specific to .NET Core.

More info

Microsoft.NetFramework.Analyzers

Latest stable version: NuGet

Analyzers for APIs specific to the desktop .NET Framework.

More info

Roslyn.Diagnostics.Analyzers

Latest stable version: NuGet

Contains analyzers specific to the .NET Compiler Platform ("Roslyn") project.

More info

Text.Analyzers

Latest stable version: NuGet

Contains analyzers for text included in code, such as comments.

Getting Started

  1. Clone the repository
  2. Restore and build: build.cmd
  3. Execute tests: test.cmd

Submitting Pull Requests

Prior to submitting a pull request, ensure the build and all tests pass using using steps 2 and 3 above.

Versioning Scheme for Analyzer Packages

See VERSIONING.md for the versioning scheme for all analyzer packages built out of this repo.

Recommended version of Analyzer Packages

Recommended Visual Studio Version: Visual Studio 2017 15.5 Preview5, RTW or later

Recommended Analyzer Package Version: Version 2.6.3, for example https://www.nuget.org/packages/Microsoft.CodeAnalysis.FxCopAnalyzers/2.6.3

Due to the fact that large number of our analyzers were based on the not-yet-shipped IOperation APIs in Roslyn, they were in beta stage and tied to a specific compiler/Visual Studio version. IOperation API shipped in Visual Studio 2017 15.5 Preview5, and we have released fully supported version 2.6.0 analyzer packages that should work on all future compiler/Visual Studio versions. Please use the following guidelines when choosing the version of analyzer packages to use on a specific version of Visual Studio/compiler toolset:

  1. Visual Studio 2015 RTW: Analyzer package Version 1.0.1, for example https://www.nuget.org/packages/Microsoft.CodeAnalysis.FxCopAnalyzers/1.0.1
  2. Visual Studio 2015 Update 1: Analyzer package Version 1.1.0, for example https://www.nuget.org/packages/Microsoft.CodeAnalysis.FxCopAnalyzers/1.1.0
  3. Visual Studio 2015 Update 2 and 3: Analyzer package Version 1.2.0-beta2, for example https://www.nuget.org/packages/Microsoft.CodeAnalysis.FxCopAnalyzers/1.2.0-beta2
  4. Visual Studio 2017 RTW (15.0), 15.1 and 15.2: Analyzer package Version 2.0.0-beta2, for example https://www.nuget.org/packages/Microsoft.CodeAnalysis.FxCopAnalyzers/2.0.0-beta2
  5. Visual Studio 2017 15.3: Analyzer package Version 2.3.0-beta1, for example https://www.nuget.org/packages/Microsoft.CodeAnalysis.FxCopAnalyzers/2.3.0-beta1
  6. Visual Studio 2017 15.5 Preview5, RTW or later: Analyzer package Version 2.6.3, for example https://www.nuget.org/packages/Microsoft.CodeAnalysis.FxCopAnalyzers/2.6.3

On Visual Studio 2017 15.5 and later releases, you can also install a custom Microsoft Code Analysis VSIX containing these analyzers as a Visual Studio extension for all your managed projects. See details here: https://marketplace.visualstudio.com/items?itemName=VisualStudioPlatformTeam.MicrosoftCodeAnalysis2017