Strong Naming #2
Description
My .NET 5.0 app is strong named for security reasons. Currently importing your package shows "... does not have a strong name." errors during build.
While the app runs despite those, would it be possible to strong name your build? This can easily be achieved by adding the following to every .csproj:
..\Foo.snk
true
Where Foo.snk is generated per sn.exe. See https://docs.microsoft.com/en-us/dotnet/standard/assembly/create-use-strong-named for more info.
My current workaround is for my code to also add a nuget reference to https://github.com/dsplaisted/strongnamer. This works, but is less than ideal. I see you are not accepting new PRs, but this behavior was not see with the Microsoft .dll. Thanks!