.NET SDK is not strong named. about secrets-manager HOT 5 OPEN

One library is enough - as it is possible to reference signed assemblies from unsigned projects - the change will not affect anyone who used it in that way. But for all who are working with signed libraries it will be more comfortable - I have to use ildasm and ilasm in my build process to sign the assembly before referencing. That step would not be needed after you sign the assembly in NuGet package - thanks

from secrets-manager.

I have signed the file in my build process but also would like to get a strong named file from Nuget package without manual steps

from secrets-manager.

Is there still a need for this? We are trying to decide if we should do this or not.

from secrets-manager.

@maksimu yes, due to third party dependencies, we will be on this .NET Framework 4.7.2 infrastructure for the foreseeable future, so the inclusion of this will make our interaction with the Keeper library a much easier experience. Also note, this is the only NuGet package we've encountered that isn't strongly named.

from secrets-manager.

from secrets-manager.