.NET Core 4.5 assembly is not strong named in the NuGet Package #3

Closed
opened 2026-01-29 22:03:20 +00:00 by claunia · 1 comment
Owner

Originally created by @daniel-chambers on GitHub (Nov 14, 2013).

In the 0.10.1.3 version of the NuGet package, the .NET 4 and PCL assemblies are strong named, but the .NET Core 4.5 assembly is not.

This is causing an assembly loading failure in my Windows 8.1 App project because I'm using another PCL package that depends on SharpCompress. When I install that other library, NuGet brings SharpCompress along as a dependency, and installs the .NET Core 4.5 version instead of the PCL version. Then at runtime, that other library fails to load SharpCompress because the .NET Core 4.5 SharpCompress assembly is not strong named, but the other package is bound to the strong named PCL version.

Originally created by @daniel-chambers on GitHub (Nov 14, 2013). In the 0.10.1.3 version of the NuGet package, the .NET 4 and PCL assemblies are strong named, but the .NET Core 4.5 assembly is not. This is causing an assembly loading failure in my Windows 8.1 App project because I'm using another PCL package that depends on SharpCompress. When I install that other library, NuGet brings SharpCompress along as a dependency, and installs the .NET Core 4.5 version instead of the PCL version. Then at runtime, that other library fails to load SharpCompress because the .NET Core 4.5 SharpCompress assembly is not strong named, but the other package is bound to the strong named PCL version.
Author
Owner

@adamhathcock commented on GitHub (Nov 23, 2013):

Fixed c4b005b3d4

Should be in next release (10.2)

@adamhathcock commented on GitHub (Nov 23, 2013): Fixed https://github.com/adamhathcock/sharpcompress/commit/c4b005b3d4afe7a9093e251b6849ae75b85e0629 Should be in next release (10.2)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/sharpcompress#3