Philips.CodeAnalysis.MsTestAnalyzers 1.7.0-prerelease.2776

This is a prerelease version of Philips.CodeAnalysis.MsTestAnalyzers.

There is a newer version of this package available.
See the version list below for details.

dotnet add package Philips.CodeAnalysis.MsTestAnalyzers --version 1.7.0-prerelease.2776

NuGet\Install-Package Philips.CodeAnalysis.MsTestAnalyzers -Version 1.7.0-prerelease.2776

This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.

<PackageReference Include="Philips.CodeAnalysis.MsTestAnalyzers" Version="1.7.0-prerelease.2776">
  <PrivateAssets>all</PrivateAssets>
  <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets>
</PackageReference>

For projects that support PackageReference, copy this XML node into the project file to reference the package.

<PackageVersion Include="Philips.CodeAnalysis.MsTestAnalyzers" Version="1.7.0-prerelease.2776" />
                    

                            Directory.Packages.props

<PackageReference Include="Philips.CodeAnalysis.MsTestAnalyzers">
  <PrivateAssets>all</PrivateAssets>
  <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets>
</PackageReference>
                    

                            Project file

For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.

paket add Philips.CodeAnalysis.MsTestAnalyzers --version 1.7.0-prerelease.2776

The NuGet Team does not provide support for this client. Please contact its maintainers for support.

#r "nuget: Philips.CodeAnalysis.MsTestAnalyzers, 1.7.0-prerelease.2776"

#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.

#:package Philips.CodeAnalysis.MsTestAnalyzers@1.7.0-prerelease.2776

#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.

#addin nuget:?package=Philips.CodeAnalysis.MsTestAnalyzers&version=1.7.0-prerelease.2776&prerelease
                    

                            Install as a Cake Addin

#tool nuget:?package=Philips.CodeAnalysis.MsTestAnalyzers&version=1.7.0-prerelease.2776&prerelease
                    

                            Install as a Cake Tool

The NuGet Team does not provide support for this client. Please contact its maintainers for support.

Introduction

Roslyn Diagnostic Analyzers are customized compiler errors providing real-time feedback to C# developers. Many Analyzers include an automatic Code Fixer. While Microsoft (and other organizations) offer many analyzers, the market is nascent. Moreover, many tools offer a rich set of rules, but lack the shift-left integration that Roslyn achieves.

We have a policy whereby Code Reviewers ask themselves if a review comment can be automated. If so, and if a Diagnostic Analyzer is the right tool for the scenario in question, and if an Analyzer does not readily exist in the market already, an issue is created to track the need. That is, all analyzers herein are based on real-world code review feedback. This project is the result. It was open-sourced in 2020.

Rules Documentation

Consult the following for details on the available rules:

Getting Started

Add the rules using Visual Studio's Package Manager, locating these packages on nuget.org. Rules are generally enabled by default. Use the .editorconfig file to enable or disable each of them and set their severity level as desired. Some rules (e.g., Avoid Duplicate Code, Avoid Static Classes) support configuration and whitelisting - again via the .editorconfig.

Debugging

Published packages include .snupkg and SourceLink. This allows symbol loading, stack traces with line numbers on exceptions, and "Go to Definition" support. However, breakpoints and step-through debugging are flaky on published Release builds (especially with Analyzers in general), due to optimizations and inlining.

For symbols and stack traces, launch a second instance of Visual Studio, attach the debugger to your primary development instance, and Load Symbols via Debug → Windows → Modules, and right-clicking on the Analyzer.

Visual Studio 2019/2022 Support

These packages reference Microsoft.CodeAnalysis version 3.6, which shipped with Visual Studio 2019 16.6.

CI/CD

Learn more about the CI/CD pipeline.

There are no supported framework assets in this package.

Learn more about Target Frameworks and .NET Standard.

.NETStandard 2.0
- No dependencies.
net8.0
- No dependencies.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version	Downloads	Last Updated
1.7.0	165	8/9/2025
1.7.0-prerelease.2776	154	8/4/2025
1.6.0	10,911	6/25/2025
1.3.0	182,209	10/23/2023
1.1.7	826,907	9/10/2021
1.1.5	56,487	4/3/2021
1.1.3	5,898	12/4/2020
1.1.2	735	12/4/2020
1.1.1	1,295	8/23/2020
1.1.0	958	7/23/2020
1.0.4	833	9/19/2020
1.0.3	1,011	7/2/2020
1.0.2	1,187	4/17/2020
1.0.1	836	4/15/2020
1.0.0	985	3/17/2020

See Changelog