NuGet strong-name

[mariopasquali]

Hi, I know this is not a popular topic, but my project requires strong-naming and thus I can't use your NuGet package as is. There is a tool named StrongNamer which should help but it doesn't work for know with .net core dotnet CLI.

The recent consensus on strong naming (which changed over the years) is that it is now recommended to strong-name NuGet packages. Would you consider strong-naming your NuGet package, or publish another package with strong-name?

[tmds]

Adding a strong name probably won't break anyone?

There is a tool named StrongNamer which should help but it doesn't work for know with .net core dotnet CLI.

Do you know what the recommended approach is when building the package on a Linux based system?

[mariopasquali]

Hi, thanks. By recommended approach, do you mean how to deal with not signed NuGet assemblies when there is a need for signed assemblies? I didn't find a tool that works on Linux for now, I guess this is just a matter of time to materialize, but I am afraid that in this case the only choice would be to build a strong name version of the assembly from the sources and use that instead of the NuGet version.

For this reason it is generally easier to have a NuGet assembly with strong name, as it works for the ones needing strong naming, without bothering the ones not using strong naming.