Failed to build when using central package version management (CPVM)

[flobernd]

My project is using the new central package version management feature (Directory.Packages.props in the root directory). If this feature is enabled, it's not allowed to specify a package version in a <PackageReference> tag.

BenchmarkDotNet build fails, because of this:

 Standard error:
   Determining projects to restore...
[...]\bin\Release\net7\a26f5fd8-3b2f-4716-a61f-af4e51ccb248\BenchmarkDotNet.Autogenerated.csproj : error NU1008: Projects that use central package version management should not define the version on the PackageReference items but on the PackageVersion items: Microsoft.DotNet.ILCompiler.

It can be fixed on your side by auto-generating a Directory.Packages.props in the output directory (e.g. \bin\Release\net7\a26f5fd8-3b2f-4716-a61f-af4e51ccb248 in this example) with the following content:

<!-- https://devblogs.microsoft.com/nuget/introducing-central-package-management/ -->
<Project>
  <PropertyGroup>
    <ManagePackageVersionsCentrally>false</ManagePackageVersionsCentrally>
  </PropertyGroup>
</Project>

This will disable the CPVM feature for all projects inside the output directory (recursively).

[adamsitnik]

Hi @flobernd

Please send a PR with the fix, you most likely need to add this setting in the following two places:

BenchmarkDotNet/src/BenchmarkDotNet/Toolchains/NativeAot/Generator.cs

Line 142 in d383135

<ValidateExecutableReferencesMatchSelfContained>false</ValidateExecutableReferencesMatchSelfContained>

BenchmarkDotNet/src/BenchmarkDotNet/Templates/CsProj.txt

Line 29 in d383135

<ValidateExecutableReferencesMatchSelfContained>false</ValidateExecutableReferencesMatchSelfContained>

[paulomorgado]

@adamsitnik,

Is this still an issue?

[adamsitnik]

Is this still an issue?

Most likely yes as we have not changed anything on our side.

[paulomorgado]

Anything I can do to move this forward?

[paulomorgado]

This might require BenchmarkDotNet to support central package management, as projects won't have versions in package references.

Or is it an issue only for the BenchmarkDotNet project?

Is there a way to get a binlog from the build BenchmarkDotNet is doing?

[adamsitnik]

Anything I can do to move this forward?

You would need to be able to reproduce it by using CPVM and then propose a fix. In theory what I posted here should be enough: #2213 (comment), but we need to test it.

Is there a way to get a binlog from the build BenchmarkDotNet is doing?

If you pass --generateBinLog BDN should generate the bin log.

BenchmarkDotNet/src/BenchmarkDotNet/ConsoleArguments/CommandLineOptions.cs

Lines 176 to 177 in 0275649

	[Option("generateBinLog", Required = false, HelpText = "Generate msbuild binlog for builds")]
	public bool GenerateMSBuildBinLog { get; set; }

[paulomorgado]

Anything I can do to move this forward?

You would need to be able to reproduce it by using CPVM and then propose a fix. In theory what I posted here should be enough: #2213 (comment), but we need to test it.

Is there a way to get a binlog from the build BenchmarkDotNet is doing?

If you pass --generateBinLog BDN should generate the bin log.

BenchmarkDotNet/src/BenchmarkDotNet/ConsoleArguments/CommandLineOptions.cs

Lines 176 to 177 in 0275649

	[Option("generateBinLog", Required = false, HelpText = "Generate msbuild binlog for builds")]
	public bool GenerateMSBuildBinLog { get; set; }

@adamsitnik, so far, 0.14.0 works fine with artifacts output and central package management.