Binaries are not strong name signed

[Tomer Rotstein]

Hi,

This is preventing us from calling the byteSize dll from a strong name assembly file (signed code can't call unsigned code).

Can you please sign your binary?

[Andreas Bjørn Hassing]

The library is comprised of a single file. Just add it to your project and you're good to go.

[Sebastian Blomberg]

This package not being strong-name signed causes issues for us as well. @omar any chance of getting the binaries strong-named signed and publishing a new version? Should be a fairly easy thing to do https://docs.microsoft.com/en-us/dotnet/standard/assembly/sign-strong-name :)

Thanks,
// Seb

[JDA88]

+1 This is preventing us to use the NuGet package and we have to integrate the sources into our own library as a workaround

[Omar Khudeira]

@JDA88, @sebbe33, @tomerrt, I just published ByteSize v2.1.2 which is strongly named. https://www.nuget.org/packages/ByteSize/2.1.2