Summary

• ProjectReference with OutputItemType="Analyzer" enables the Roslyn analyzers during in-solution builds, but does not cause the DLL to appear in the NuGet package under analyzers/dotnet/cs/
• As a result, consumers of the OpenCvSharp4 NuGet package never saw the OCVS001–OCVS005 warnings (e.g. mat.Row(1).At<byte>(1))
• Fix: add an explicit None item with Pack="true" and PackagePath="analyzers/dotnet/cs" pointing at the built OpenCvSharp.Analyzers.dll

What changed

src/OpenCvSharp/OpenCvSharp.csproj — added:

<None Include="..\OpenCvSharp.Analyzers\bin\$(Configuration)\netstandard2.0\OpenCvSharp.Analyzers.dll"
      Pack="true"
      PackagePath="analyzers/dotnet/cs"
      Visible="false" />

Verification

Ran dotnet pack before and after:

• Before: analyzers/dotnet/cs/ absent from .nupkg
• After: analyzers/dotnet/cs/OpenCvSharp.Analyzers.dll present in .nupkg

Reviewer notes

The None item references the build output path, so OpenCvSharp.Analyzers must be built before packing OpenCvSharp. This ordering is already guaranteed in normal solution builds and CI (the ProjectReference dependency ensures the analyzer project builds first).

Summary by CodeRabbit

• Chores
  • Improved NuGet package configuration to ensure analyzers are properly included in the distributed package.