Please release a signed version of LazyCache

[themightygugi]

Hi @alastairtree

Tnx for a great library. Really enjoy working with it and it has saved me a lot of time and effort.

Would you be so kind as to release a signed version of the NuGet package, so I can use LazyCache in my signed desktop applications.

tnx

[alastairtree]

Hi, and thanks. Do you mean sign the nuget package or just the dll/strong naming?

See these docs for some background - http://blog.nuget.org/20150203/package-signing.html and https://msdn.microsoft.com/en-GB/library/xc31ft41%28v=vs.110%29.aspx?f=255&MSPPError=-2147217396

[SamJongenelen]

Please strongly sign the assembly inside the NuGet package, yes

[PureKrome]

Food for thought re signing: https://github.com/octokit/octokit.net/issues/405

[alastairtree]

More thought food

• https://github.com/NuGet/Home/wiki/Package-signing
• https://docs.microsoft.com/en-us/nuget/create-packages/sign-a-package
• https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/strong-naming

[xmedeko]

Some well known C# open source libs stops releasing strong signed DLLs, e.g. see https://github.com/MahApps/MahApps.Metro/blob/develop/docs/release-notes/1.6.0.md#breaking-change

You can compile strong named DLL by yourself, or use the Strong Namer or Strong-Name Signer.

[GBurlakova]

StrongNamer is a good alternative, but it causes issues in debug mode, so if you release a strong-named version of the library, that would be great and very helpful.

[alastairtree]

Some more info on package signing that makes me think it's still not a great idea https://haacked.com/archive/2019/04/03/nuget-package-signing/