You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Binaries contained in your NuGet 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
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.
The text was updated successfully, but these errors were encountered:
Binaries contained in your NuGet 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:
Thanks in advance.
The text was updated successfully, but these errors were encountered: