You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@pombredanne I checked it, basically, what i do, is I use AssemblyVersion instead of Assembly Version.
I got AssemblyVersion is null for tests\packagedcode\data\win_pe\Microsoft.Practices.EnterpriseLibrary.Caching.dll and tests\packagedcode\data\win_pe\Moq.Silverlight.dll
But in previous it is pointing to "Assembly Version": "2.0.0.0", for tests\packagedcode\data\win_pe\Microsoft.Practices.EnterpriseLibrary.Caching.dll
and "Assembly Version": "4.2.1507.118", for tests\packagedcode\data\win_pe\Moq.Silverlight.dll.
I think there might be some issue I raise a PR soon regarding this.
alok1304
added a commit
to alok1304/scancode-toolkit
that referenced
this issue
Jan 23, 2025
We collect binary metadata in DLLs.
See https://github.com/nexB/scancode-toolkit/blob/4f49985c26b6b8f951f116dfa3fe39ce27bd4ce8/src/packagedcode/win_pe.py#L110
But see this publication:
https://learn.microsoft.com/en-us/troubleshoot/developer/dotnet/framework/general/assembly-version-assembly-file-version
We may also wrongly use "Assembly Version" instead of "AssemblyVersion"
The text was updated successfully, but these errors were encountered: