StyleCop.MSBuild
Adds official StyleCop MSBuild targets to your project for running StyleCop analysis with every build. Includes official StyleCop binaries. Works both on a developer workstation (with or without Visual Studio) and on a build server. Does not require installation of StyleCop on any machine. Compatible with NuGet package restore. For update notifications follow https://twitter.com/adamralph. Come and chat to fellow developers about StyleCop and StyleCop.MSBuild at https://jabbr.net/#/rooms/stylecop/. NOTE: There is a known issue with NuGet Package Manager versions 1.8 to 2.0. See http://nuget.codeplex.com/workitem/2253 for details. If you are using NuGet Package Manager versions 1.8 to 2.0, you are advised to upgrade to version 2.1 or later before installing or updating StyleCop.MSBuild. If you are unable to upgrade to NuGet Package Manager version 2.1 or later and you have problems installing or updating StyleCop.MSBuild, see http://nuget.codeplex.com/workitem/2253 for a workaround. This issue was resolved in NuGet Package Manager version 2.1. NOTE: If your solution is currently using StyleCop.MSBuild.4.7.17.0 or earlier, updating to a later version will NOT work. Instead of updating, uninstall your current version and then install a later version. See http://adamralph.com/2012/04/17/introducing-stylecop-msbuild/ for an explanation.
Install
dotnet add package StyleCop.MSBuild --version 4.7.47
Install-Package StyleCop.MSBuild -Version 4.7.47
<PackageReference Include="StyleCop.MSBuild" Version="4.7.47" />
Frameworks
No framework metadata available.
Dependencies
No declared dependencies.
Adoption guide
Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.
No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.
No target framework metadata is available. Confirm compatibility in a representative project before standardising on this package.
How to read this guidance
Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.
Useful next steps
Move from package metadata to a concrete selection or review workflow.