Referenced Assembly doesn't have a strong name

[JaegarGrisha]

First of all, kudos on building such an amazing library!! Thank you to you and everyone involved in the project!

Onto the issue:
I'm tyring to include this package directly into one of my projects. But when I'm trying to build it, I'm facing this issue:
CSC : error CS8002: Referenced assembly 'Clipper2Lib, Version=1.2.2.0, Culture=neutral, PublicKeyToken=null' does not have a strong name.
Could you please publish a signed version of the package on nugget so that I can directly use without having to manually sign it myself every time there's an update?

[lutz]

That's what I would like to see.

[AngusJohnson]

Thanks for the feedback. I'm afraid my knowledge of C# is quite limited and I'm only barely competent in producing nugget packages. To do what you're requesting, it seems I'd need a certificate from a Signing Authority, which usually require payment. And I'm rather disinclined to spend money just so I can share my open source freeware.

[lutz]

Thanks for answering, From my perspective you didn`t need a external certificate. You can use Visual Studio to enable "Strong naming" and also use Visual Studio to create the *.snk file (manual) which is needed for.

You can check in your key to github because this is source code available. Microsoft itself described it here:

If you are an open-source developer and you want the identity benefits of a strong-named assembly for better compatibility with .NET Framework, consider checking in the private key associated with an assembly to your source control system.

[AngusJohnson]

OK, I'll certainly consider this, but I'm currently preoccupied with other stuff that's higher priority.