Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.97%. Comparing base (fe673ec) to head (82ed632).
Report is 111 commits behind head on main.

@@            Coverage Diff             @@
##             main    #9840      +/-   ##
==========================================
+ Coverage   74.31%   78.97%   +4.65%     
==========================================
  Files         536      538       +2     
  Lines       23189    23319     +130     
  Branches     4056     4049       -7     
==========================================
+ Hits        17234    18417    +1183     
+ Misses       4853     3774    -1079     
- Partials     1102     1128      +26     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Is there a reason why we need to publish to NuGet first before adding the benchmark project?

Is there a reason why we need to publish to NuGet first before adding the benchmark project?

It's because I want to write benchmarks that targeting following two versions in single benchmark.

1. NuGet published version (Baseline)
2. Local source build version

Note:
It's not tested yet, that it can referencing same assemblies with different versions aliases (by referencing using extern alias).
If it's not possible. It need to switch two version by using csproj settings.

And it's also can be used to compare multiple NuGet versions benchmark.(Example)

Make sense