CsAssay.Analyzers
0.1.2
dotnet add package CsAssay.Analyzers --version 0.1.2
NuGet\Install-Package CsAssay.Analyzers -Version 0.1.2
<PackageReference Include="CsAssay.Analyzers" Version="0.1.2"> <PrivateAssets>all</PrivateAssets> <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets> </PackageReference>
<PackageVersion Include="CsAssay.Analyzers" Version="0.1.2" />
<PackageReference Include="CsAssay.Analyzers"> <PrivateAssets>all</PrivateAssets> <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets> </PackageReference>
paket add CsAssay.Analyzers --version 0.1.2
#r "nuget: CsAssay.Analyzers, 0.1.2"
#:package CsAssay.Analyzers@0.1.2
#addin nuget:?package=CsAssay.Analyzers&version=0.1.2
#tool nuget:?package=CsAssay.Analyzers&version=0.1.2
CSharpAssay analyzers
CsAssay.Analyzers supplies the admitted CSharpAssay Roslyn diagnostics to
editor and build hosts. The package embeds the analyzer, its three
CSharpAssay-owned runtime dependencies under analyzers/dotnet/cs, and a
transitive MSBuild enforcement target.
<PackageReference Include="CsAssay.Analyzers"
Version="0.1.2"
PrivateAssets="all" />
The package is a research preview. Only rules marked Admitted can block a
CSharpAssay release verdict. See the repository documentation for policy,
suppression, staged adoption, installation, and rollback guidance. The six
Phase 6 contextual/heuristic rules are informational and cannot block in
0.1.2.
CsAssayEnforceOnBuild defaults to true. Admitted violations therefore fail
ordinary dotnet build; disabling analyzers or listing an admitted CSharpAssay
rule in NoWarn fails with an explicit gate error. Set the property to false
only for a reviewed emergency rollback. Under global warnings-as-errors, that
rollback keeps CSharpAssay diagnostics visible while exempting only admitted
CSharpAssay IDs from error promotion; unrelated warnings remain errors.
The analyzer package does not consume CLI Core/Shell policy. Its enforcement scope is the project that installs it, so keep the reference on reviewed core projects rather than installing it centrally across shell projects. The authoritative CLI remains required for graph, all-target-framework, configured-test, boundary-policy, and completeness evidence.
Learn more about Target Frameworks and .NET Standard.
This package has 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.