Binaries contained in nuget(SharpIPPNext) are not generated using a strong name

[alonsoto]

We opened this issue here because in SharpIppNext fork issues are not enabled.

Binaries contained in your NuGet(SharpIPPNext) are not generated using a strong name, when we use your asset as third party we receive the advise from Cybersecure auditory.

Use strong-naming have some benefits explained by Microsoft official documentation

https://learn.microsoft.com/en-us/dotnet/standard/library-guidance/strong-naming

The benefits of strong naming on .NET Framework are:

• The assembly can be referenced and used by other strong-named assemblies.
• The assembly can be stored in the Global Assembly Cache (GAC).
• The assembly can be loaded side by side with other versions of the assembly. Side-by-side assembly loading is commonly required by applications with plug-in architectures.

Thanks in advance.

[danielklecha]

@alonsoto I updated my fork to generate a standard and strong-named version.
Search for SharpIppNext.StrongName version 1.0.11.
I verified it with command sn -v SharpIpp.dll and it was valid.

I enabled issues on my fork.

Close the issue if everything will work.

[alonsoto]

Hi @danielklecha we checked with tool an this is the result.

We are little bit puzzled.

Thanks in advance.

[danielklecha]

@alonsoto I configured GitHub Action to generate two packages. SharpIppNext and SharpIppNext.StrongName. You should use this second package.