search

bilaldursun1 / nettopologysuite

Automatically exported from code.google.com/p/nettopologysuite
0 stars 0 forks source link

Signing of assemblies #157

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
some months ago, I opened issue #149. In it we concluded on not signing the 
assemblies.

However, now that I've rolled out the packages in another project, I found out 
I _DO_ need signed assemblies...

Original issue reported on code.google.com by spanne...@gmail.com on 10 Sep 2013 at 9:36

GoogleCodeExporter commented 9 years ago 
Do you mind signing them yourself?

Original comment by felix.ob...@netcologne.de on 2 Oct 2013 at 9:53

GoogleCodeExporter commented 9 years ago

Original comment by diegogu...@gmail.com on 13 Jan 2014 at 4:13

GoogleCodeExporter commented 9 years ago 
As NTS + GeoAPI are released on nuget and widely used projects like Lucene.NET 
and RavenDB are dependent on them, it doesn't make sense to require users to 
sign the assemblies themselves.

The assemblies that are shipped via nuget need to be signed already, so 
projects that _are_ signed (most of the big and commonly used ones) can use 
them from nuget and not manually compile and sign them.

Please re-open and sign the assemblies, and then release an updated nuget 
package.

Original comment by itamar.s...@gmail.com on 22 Apr 2014 at 2:01

GoogleCodeExporter commented 9 years ago 
actually, assemblies are signed now, as needed of #110

Original comment by diegogu...@gmail.com on 22 Apr 2014 at 6:56