HttpClientFactoryLite.dll is not strong-named - Githubissues

uhaciogullari / HttpClientFactoryLite

HttpClientFactory with no baggage

Apache License 2.0

62 stars 7 forks source link

HttpClientFactoryLite.dll is not strong-named #8

Open daiplusplus opened 3 years ago

daiplusplus commented 3 years ago

Describe the bug

HttpClientFactoryLite.dll is not strong-named
So it cannot be used from a project that is strong-named, as strong-named assemblies can only load other strong-named assemblies.

To Reproduce

Steps to reproduce the behavior:

Create a new .NET Framework 4.8 Console project.
Give that project a strong-name (VS > Project Properties).
Add a NuGet reference to HttpClientFactoryLite.
Instantiate a HttpClientFactoryLite.HttpClientFactory instance in your Main method.
The project builds, but fails to run with this exception:

Error: System.IO.FileLoadException: Could not load file or assembly 'HttpClientFactoryLite, Version=0.4.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required. (Exception from HRESULT: 0x80131044).

Expected behavior

I expected this assembly to be strong-named.

Screenshots

N/A

Additional context

N/A