DMG files broken because of assembly signing

[RickRockhold]

DiscUtils uses strongly-named assemblies, but the referenced lzfse-net package is not strongly signed, so it can't be loaded. This means the most modern DMG files can't be read.

[LTRData]

Signing strong named assemblies is mostly deprecated now so this typically does not matter. That is, unless you need to use the library in .NET Framework applications where you need to import the library into the GAC. That requires strongly named assemblies and only strongly named assemblies can be referenced from them.

https://github.com/dotnet/runtime/blob/main/docs/project/strong-name-signing.md

[RickRockhold]

I'm using the library with .NET 4.7.2, and I'm not importing into the GAC. But the library doesn't work--.NET won't allow DiscUtils to load lzfse-net, because .NET won't let assemblies with a strong name to load an assembly without a strong name.

So in this configuration, the library is unusable.

[LTRData]

I see. I think the easiest solution to such scenarios is to build another version without the signing. Since the signing is needed in some other cases.

Or maybe the other way around, maybe the packages should nowadays contain not-signed files and those who need strongly named files could generate a key and build their own.