FazBrowse GitHub Viewer
|
Trending
|
URL:
|
Home
Tools:
[Download Repo ZIP]
[View Raw Code]
[Original HTTPS Page]
SharpMap/SharpMap.SqlServerSpatialObjects/ReadMe.txt at develop · SharpMap/SharpMap · GitHub
SharpMap
SharpMap
Repository navigation
Code
Issues
42
(42)
Pull requests
6
(6)
Discussions
Actions
Projects
Wiki
Security and quality
Insights
Expand file tree
Breadcrumbs
SharpMap
/
SharpMap.SqlServerSpatialObjects
/
ReadMe.txt
Copy path
More file actions
More file actions
Latest commit
History
History
History
60 lines (48 loc) · 3.24 KB
Breadcrumbs
SharpMap
/
SharpMap.SqlServerSpatialObjects
/
ReadMe.txt
Copy path
File metadata and controls
60 lines (48 loc) · 3.24 KB
Raw
Copy raw file
Download raw file
Open symbols panel
Edit and raw actions
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
Update Sep 2019: Resolve SqlServer dependencies and loading native types
1) SqlServer dependencies (x32 and x64) now defined by NuGet package Microsoft.SqlServer.Types
This includes:
Microsoft.SqlServer.Types.dll
msvcr120.dll (x32/x64)
SqlServerSpatial140.dll (x32/x64)
2) Loading x32 or x64 native types at runtime now handled internally by static constructors
3) Your project should only reference SharpMap.SqlServerSpatialObjects:
a) Your project does NOT need NuGet package Microsoft.SqlServer.Types
b) Your project does NOT need to explicitly load SqlServer types at runtime
c) Your project most likely requires a BINDING REDIRECT (see WinformSamples app.config)
</runtime>
</assemblyBinding>
<dependentAssembly>
<assemblyIdentity name="Microsoft.SqlServer.Types" publicKeyToken="89845dcd8080cc91" culture="neutral" />
<bindingRedirect oldVersion="10.0.0.0-15.0.0.0" newVersion="14.0.0.0" />
</dependentAssembly>
</assemblyBinding>
</runtime>
d) If you remove NuGet package Microsoft.SqlServer.Types from your project, you will probably need manually delete
sub-folder "SqlServerTypes". Otherwise, SqlServer dependencies may not be copied across during build.
=================================================================================================================================
In order to use this project you need to add a reference to the
"Microsoft SQL Server System CLR Types".
If you have SqlServer2008 (Express) installed on your machine you'll probably find in somewhere
in the installation path of it. On my machine the path is:
C:\Program Files\Microsoft SQL Server\100\SDK\Assemblies\Microsoft.SqlServer.Types.dll
If you do not have SqlServer 2008 on your machine, all you need is download some files
from the "Microsoft SQL Server 2008 Feature Pack, October 2008":
http://www.microsoft.com/downloads/en/details.aspx?FamilyId=228DE03F-3B5A-428A-923F-58A033D316E1&displaylang=en
Look for "Microsoft SQL Server System CLR Types"
Enjoy
FObermaier
=================================================================================================================================
Update Nov 2018: Added support for SqlGeography
SqlServer2008Ex.cs
SqlGeographyConverter.cs (new class)
SpatialOperationsEx.cs (basic support for Geography)
SpatialRelationsEx.cs (basic support for Geography)
Several more recents approaches were also considered, but would have caused breaking changes:
1) Drop reference to Microsoft.SqlServer.Types and replace with NuGet Microsoft.SqlServerTypes v14.0.1016.290
This package support x86 and x64, and also includes SqlServerSpatialxxx.dll (no need to install any other Sql Server binaries).
Also requires binding redirects, and native SQL assemblies must be explicitly loaded at runtime by client (breaking change)
2) Use NuGet NetTopologySuite.Io.SqlServerBytes (released Oct 2018) instead of SqlGeometryConverter.cs
This package provides comprehensive conversion between NTS geometry and SQL Server geometery/geography types, but targets NetStandard 2.0.
Also, SqlGeometryConverter.cs implements custom exception handling.
Regards
Tim
Back
|
FazBrowse Home
|
New Git URL