Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Binaries contained in nuget are not generated using a strong name #119

Open
alonsoto opened this issue Sep 13, 2024 · 0 comments
Open

Binaries contained in nuget are not generated using a strong name #119

alonsoto opened this issue Sep 13, 2024 · 0 comments

Comments

@alonsoto
Copy link

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:

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant