We have started a discussion on GitHub for further development of Sql Server 2012 features and naming conventions, feel free to join in: https://github.com/suryapratap/Nhibernate.Spatial/issues/6
-Andreas On Monday, March 3, 2014 1:04:36 PM UTC+1, Surya Pratap wrote: > > Yes, > we did think of pushing SqlServer2012 as a separate package. > but that is just talk right now. > > I am not sure what will be good, a per-vendor-per-version packages for the > db's or just a per-vendor package > > > The first option puts in a lot of dependencies as soon as the vendors > release new versions, later a lot of code migration will need to be done if > we start depreciating older packages. But this will allow the user to > upgrade selectively. One of the reasons for thinking of Sql2008 and Sql2012 > is that the spatial dll's for the drivers have changed between versions. I > am not sure about the case for other databases. > > > The second option will force users to upgrade db specific dll even if they > are still using an older db version (which might not be as bad as it > sounds) but it will allow deployment with fewer dependent dll's and easier > maintenance. > > All suggestions are welcome, contributors even more so ;) > > > Regards > Surya > > > > > On Mon, Mar 3, 2014 at 3:52 PM, Stephen Bohlen <[email protected]<javascript:> > > wrote: > >> That's awesome news -- thanks for the effort! Great to see NH-SP >> starting to catch up to a dependency on the latest NH! >> >> One suggestion re: the .MsSql2008 package...when you get to the pt where >> the package goes GA (e.g., "non-pre") I wonder whether it might be a good >> idea to add to the descr. of that package that the 2008 package supports >> SQL Server's Spatial extensions up through SQL Server 2012 (?). I'm >> thinking that a consumer of that package would otherwise have no way of >> knowing that it supported other that SQL Server 2008 (short of perhaps >> reading release notes which usually aren't visible until after the package >> is installed). >> >> Right now, the description of all three packages is identical: >> >> NHibernate.Spatial is a library of spatial extensions for NHibernate, and >>> allows you to connect NHibernate to a spatially enabled database and >>> manipulate geometries in HQL or in .NET code using NetTopologySuite, >>> providing you with a fully integrated GIS programming experience. >> >> >> If you add to the description something along the lines of .... >> >> This package supports <insert database name here> versions >>> <lowest-version> to <highest-version>. >> >> >> ...it might help make things clearer. >> >> Now that I think about it, I guess a related question that comes to mind >> is this: how would a consumer of these packages for MySQL or PostGIS know >> what version(s) of those DBs are supported either? Should there be an >> e.g., .MySql5 suffix considered for the MySql package? >> >> Once you set a package name in NuGet, that's an irreversible decision (at >> least in re: users updating to the newer packages via NuGet tooling), so we >> should probably make sure we're using a naming convention that makes >> coherent sense across packages before these are released for GA. Since few >> users (in my experience) do much reading about a package beyond inspecting >> its name in the NuGet dialog, the name is the first, best opportunity to >> 'advertise' the package's intent to consumers. >> >> What are other's thoughts on this --? >> >> Steve Bohlen >> [email protected] <javascript:> >> http://blog.unhandled-exceptions.com >> http://twitter.com/sbohlen >> >> >> On Mon, Mar 3, 2014 at 4:39 AM, Andreas Ravnestad >> <[email protected]<javascript:> >> > wrote: >> >>> Hi all, >>> >>> Building on the excellent work of Richardo Stuven and Surya Pratap, >>> there are now NuGet packages available for NHibernate.Spatial built against >>> NHibernate 3.3.3: >>> https://www.nuget.org/packages/NHibernate.Spatial.MsSql2008/ >>> https://www.nuget.org/packages/NHibernate.Spatial.MySQL/ >>> https://www.nuget.org/packages/NHibernate.Spatial.PostGis/ >>> >>> I expect to maintain these packages in collaboration with Mr. Pratap and >>> keep them up to date alongside NHibernate, including the upcoming 4.x >>> release. Note that the Oracle package is not available at this time. Also >>> note that the MsSql2008 package *IS* compatible with SQL Server 2012. >>> >>> The packages are currently marked as pre-release, meaning that to >>> install them you must add the -pre flag in the NuGet package manager >>> console. Here are the commands: >>> Install-Package NHibernate.Spatial.MsSql2008 -Pre >>> Install-Package NHibernate.Spatial.MySQL -Pre >>> Install-Package NHibernate.Spatial.PostGis -Pre >>> >>> Contributors to this project are more than welcome. You can fork it >>> here: https://github.com/suryapratap/Nhibernate.Spatial >>> >>> Thanks, >>> Andreas Ravnestad (@andrerav) >>> >>> -- >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "nhibernate-development" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]<javascript:> >>> . >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "nhibernate-development" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]<javascript:> >> . >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- --- You received this message because you are subscribed to the Google Groups "nhibernate-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
