Nuget assemblies bad version from 9.0.4

[julichan]

Description

Hello,

It seems that System.Threading.Channels nugget assemblies have proper assembly version on dll from 9.0.0 to 9.0.3 which are 9.0.0.x but in both 9.0.4 and 9.0.5 nugets, this is set to 9.0.0.0. I'm not sure how the framework can distinguish between dll versions... This is causing problems with assembly bindings.

Thanks.

Reproduction Steps

Just get the related nuggets, extract it, check any dll through PowerShell with [Reflection::Assembly name]::GetAssemblyName() method.

Expected behavior

The nugget patch version should be identical to assembly révision version.

Actual behavior

The assembly révision version is set to 0 making nugget usage with assembly bindings require much more work to update.

Regression?

This worked until version 9.0.3 and fails from 9.0.4

Known Workarounds

Manually open necessary nugets and scan them with PowerShell to get the right assembly bindings version

Configuration

.Net 8 but I think no this does not apply

Other information

Other nugets may be impacted

[ViktorHofer]

I don't see that difference when I compare 9.0.3 with 9.0.4.

9.0.3:

9.0.4:

@julichan what am I missing? The AssemblyVersion for any other assembly than .NET Frameworks is intentionally pinned to 9.0.0.0. That's by design.

[julichan]

What you re showing me is strange. The nuget in my cache for 9.0.3 is correctly set to 9.0.0.3 but from 9.0.4 and 9.0.5, I get only 9.0.0.0.
Until now the project I work on had an assembly binding set to 9.0.0.3 but when I updated the nuget to 9.0.4 and the assembly binding to 9.0.0.4, after build the runtime states that it couldn t find the assembly for version 9.0.0.4. when it worked with 9.0.0.3.
I don't know what tool you are using to check the version but PowerShell proved that the version in the dll was wrong.

[julichan]

Alright, I went on and checked all DLLs in 9.0.4 nuget. It seems net452 is set correctly but netstandard2.0 and other are different.

I compared with Microsoft.bcl.asyncinterface and it does not have the problem