Strong name sign json-ld.net assemblies

Question

Strong name sign json-ld.net assemblies

Closed this issue 5 years ago · 7 comments

...preferably with enhanced strong naming.

Answer 1 · 2018-07-24T09:08:47.000Z

How do we best handle this in an open-source environment? Open to suggestions

Answer 2 · 2018-07-24T15:39:03.000Z

An option would be to join the .NET Foundation as they provide code signing services to open source projects. See: https://dotnetfoundation.org/about

Answer 3 · 2018-08-04T19:24:49.000Z

Any thoughts on .Net Foundation idea @asbjornu ? Do you know if other members of the json-ld wg would have any issues with membership?

Answer 4 · 2018-09-27T07:57:15.000Z

A bit related to the .NET foundation: would it make sense to make sure there is a standard RDF representation among .NET RDF projects? There is already an RDFJS standard that can be used as an example: http://rdf.js.org/

Answer 5 · 2018-09-27T09:21:56.000Z

Will take a look or feel free to suggest initial steps

Answer 6 · 2018-09-27T21:36:26.000Z

I’m not opposed to .NET Foundation, but I am to strong naming. Perhaps the rationale and experience is different with .NET Core, but back in the framework days, strong naming causes nothing but trouble, with very few real benefits.

If you need a strong name for an assembly, you can strong name it yourself with Strong Namer.

Answer 7 · 2020-05-04T13:39:55.000Z

This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs. Thank you for your contributions.