NTS should reference GeoAPI 1.7.1

bilaldursun1 / nettopologysuite

Automatically exported from code.google.com/p/nettopologysuite

0 stars 0 forks source link

NTS should reference GeoAPI 1.7.1 #149

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

GeoAPI 1.7.1 was released a few days after NTS 1.13. Other libraries refer 
GeoAPI 1.7.1 now, NuGet will also grab 1.7.1 on update. However, NTS 1.13 is 
build explicitly with 1.7.0, thus wrecking every bit of code that uses a 
combination of NTS & another c# library that uses GeoAPI. (For instance, 
NHibernate Spatial, SharpMap, DotSpatial)

When will a version with GeoAPI 1.7.1 be released to NuGet?

Original issue reported on code.google.com by spanne...@gmail.com on 23 May 2013 at 7:18

GoogleCodeExporter commented 9 years ago

please post questions like this one in the google groups forum:
https://groups.google.com/forum/#!forum/nettopologysuite

Original comment by diegogu...@gmail.com on 23 May 2013 at 7:37

Changed state: Invalid

GoogleCodeExporter commented 9 years ago

Well, seeing as this is a code issue and you are maintaining both GeoApi as 
NTS, I consider this a bug. I'm not able to release anything because the world 
moved to GeoAPI 1.7.1 and I require both NTS as other libraries for my 
projects...

So I could either ask "everybody" to downgrade to 1.7.0 or I could ask the 
creator of both NTS as GeoApi to sync up. But I will also add a topic in the 
google groups forum.

Original comment by spanne...@gmail.com on 23 May 2013 at 8:10

GoogleCodeExporter commented 9 years ago

I will have prepared a new NuGet package by the end of this month.

Original comment by felix.ob...@netcologne.de on 25 Jun 2013 at 11:38

GoogleCodeExporter commented 9 years ago

Awesome Felix, thanks!

Original comment by spanne...@gmail.com on 25 Jun 2013 at 2:47

GoogleCodeExporter commented 9 years ago

ATM GeoAPI and NTS are signed assemblies. I'm considering to remove the signing 
to avoid the problems you and others are having due to version mismatch.

Original comment by felix.ob...@netcologne.de on 26 Jun 2013 at 9:11

GoogleCodeExporter commented 9 years ago

Now here is the question. Do you need/rely on signed assemblies?

Original comment by felix.ob...@netcologne.de on 26 Jun 2013 at 9:11

GoogleCodeExporter commented 9 years ago

I don't rely on signed asseblies myself at this very moment, but I have no clue 
about others.

Original comment by spanne...@gmail.com on 26 Jun 2013 at 9:45

GoogleCodeExporter commented 9 years ago

n the past I've signet NTS assembly because I need to use the library
inside SqlServer 2008: now this isn't a mandatory thing, so no cons
for me, except for the nuget thing: http://nuget.codeplex.com/discussions/247827

Original comment by diegogu...@gmail.com on 26 Jun 2013 at 12:01

GoogleCodeExporter commented 9 years ago

Just released 1.13.1 as nuget package

Original comment by felix.ob...@netcologne.de on 10 Jul 2013 at 1:06

Changed state: Fixed

GoogleCodeExporter commented 9 years ago

Well.... I just found out I DO have a scenario where I need signed 
assemblies... :(

Original comment by spanne...@gmail.com on 10 Sep 2013 at 9:22

GoogleCodeExporter commented 9 years ago

Signing is important, since its otherwise impossible to use the .dlls in a 
signed assembly

Original comment by svalent...@gmail.com on 10 Jul 2014 at 12:57

GoogleCodeExporter commented 9 years ago

Agreed, we are now still using an older version because the newer assemblies 
aren't signed.

Original comment by spanne...@gmail.com on 11 Jul 2014 at 6:05