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.
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.