See the version list below for details.
Install-Package System.Spatial -Version 5.6.0
dotnet add package System.Spatial --version 5.6.0
<PackageReference Include="System.Spatial" Version="5.6.0" />
paket add System.Spatial --version 5.6.0
#r "nuget: System.Spatial, 5.6.0"
// Install System.Spatial as a Cake Addin #addin nuget:?package=System.Spatial&version=5.6.0 // Install System.Spatial as a Cake Tool #tool nuget:?package=System.Spatial&version=5.6.0
Contains classes and methods that facilitate geography and geometry spatial operations. Targets .NET 4.0, Silverlight 4.0 or .NET Portable Lib with support for .NET 4.0, SL 4.0, Win Phone 7, and Win 8. Localized for CHS, CHT, DEU, ESN, FRA, ITA, JPN, KOR and RUS.
|.NET Framework||net40 net403 net45 net451 net452 net46 net461 net462 net463 net47 net471 net472 net48|
This package has no dependencies.
NuGet packages (159)
Showing the top 5 NuGet packages that depend on System.Spatial:
This version of the library supports earlier versions of the Microsoft OData (V1-V3) protocol only and is not under active development. OData V1-V3 has been superseded by OData V4, which is an industry standard published by OASIS and ratified by ISO. OData V4 is supported through the OData V4 compliant core libraries available at: https://www.nuget.org/packages/Microsoft.OData.Core/ with support documentation available at: https://odata.github.io/odata.net. Note that Asp.Net developers can build OData V4 services using the higher-level OData V4 WebAPI libraries available at: https://www.nuget.org/packages/Microsoft.AspNet.OData/ with support documentation available at: https://odata.github.io/WebApi/. Classes to serialize, deserialize and validate OData payloads. Enables construction of OData producers and consumers. Targets .NET 4.0, Silverlight 4.0 or .NET Portable Lib with support for .NET 4.0, SL 5.0, Win Phone 8, Win Phone 8.1, and Win 8. Localized for CHS, CHT, DEU, ESN, FRA, ITA, JPN, KOR and RUS.
This is the .NET Client Library for Microsoft Azure Active Directory Graph API. Learn more about Azure AD Graph API @ https://msdn.microsoft.com/Library/Azure/Ad/Graph/howto/azure-ad-graph-api-operations-overview. NOTE: Azure AD Graph API functionality is also available through Microsoft Graph, a unified API that also includes APIs from other Microsoft services like Outlook, OneDrive, OneNote, Planner, and Office Graph, all accessed through a single endpoint with a single access token. Find out more about Microsoft Graph @ http://graph.microsoft.com, and find the Microsoft Graph .Net Client Library @ https://www.nuget.org/packages/Microsoft.Graph and the open source code and further documentation @ https://github.com/microsoftgraph/msgraph-sdk-dotnet Usage information is available on our AAD Graph blog @ http://blogs.msdn.com/b/aadgraphteam/archive/2014/12/12/announcing-azure-ad-graph-api-client-library-2-0.aspx and sample usage on github @ https://github.com/AzureADSamples/WebApp-GraphAPI-DotNet and https://github.com/AzureADSamples/ConsoleApp-GraphAPI-DotNet.
This package contains Windows Azure Media Service library 184.108.40.206 for .NET.
Adds an image service and cache to ImageProcessor.Web that uses Azure Blob Containers. If you use ImageProcessor.Web please get in touch via my twitter @james_m_south Feedback is always welcome
A NuGet package that contains a set of extension methods and helpers for the Windows Azure Media Services SDK for .NET.
GitHub repositories (101)
Showing the top 5 popular GitHub repositories that depend on System.Spatial:
.NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
Store securely encrypted backups in the cloud!
Experience, Learn and Code the latest breakthrough innovations with Microsoft AI
The open source diagnostics platform for the web
Orchard is a free, open source, community-focused Content Management System built on the ASP.NET MVC platform.
What is in the release:
Visual Studio 2013 Support
The WCF DS 5.6.0 tooling installer has support for Visual Studio 2013. If you are using Visual Studio 2013 and would like to consume OData services, you can use this tooling installer to get Add Service Reference support for OData. Should you need to use one of our prior runtimes, you can still do so using the normal NuGet package management commands (you will need to uninstall the installed WCF DS NuGet packages and install the older WCF DS NuGet packages).
All of our client-side libraries now have portable library support. This means that you can now use the new JSON format in Windows Phone and Windows Store apps. The core libraries have portable library support for .NET 4.0, Silverlight 5, Windows Phone 8 and Windows Store apps. The WCF DS client has portable library support for .NET 4.5, Silverlight 5, Windows Phone 8 and Windows Store apps. Please note that this version of the client does not have tombstoning, so if you need that feature for Windows Phone apps you will need to continue using the Windows Phone-specific tooling.
URI Parser Integration
The URI parser is now integrated into the WCF Data Services server bits, which means that the URI parser is capable of parsing any URL supported in WCF DS. We have also added support for parsing functions in the URI Parser.
Public Provider Improvements - Reverted
In the 5.5.0 release we started working on making our providers public. In this release we hoped to make it possible to override the behavior of included providers with respect to properties that don’t have native support in OData v3, for instance enum and spatial properties. Unfortunately we ran into some non-trivial bugs with $select and $orderby and needed to cut the feature for this release.
Public Transport Layer
In the 5.4.0 release we added the concept of a request and response pipeline to WCF Data Service Client. In this release we have made it possible for developers to directly handle the request and response streams themselves. This was built on top of ODataLib's IODataRequestMessage and IODataResponseMessage framework that specifies how requests and responses are sent and recieved. With this addition developers are able to tweak the request and response streams or even completely replace the HTTP layer if they so desire. We are working on a blog post and sample documenting how to use this functionality.
In this release we took a couple of breaking changes. As these bugs are tremendously unlikely to affect anyone, we opted not to increment the major version number but we wanted everyone to be aware of what they were:
- Developers using the reading/writing pipeline must write to Entry rather than Entity on the WritingEntryArgs
- Developers should no longer expect to be able to modify the navigation property source in OnNavigationLinkStarting and OnNavigationLinkEnding
- Developers making use of the DisablePrimitiveTypeConversion knob may see a minor change in their JSON payloads; the knob previously only worked for the ATOM format
- Fixes a performance issue with models that have lots of navigation properties
- Fixes a performance issue with the new JSON format when creating or deleting items
- Fixes a bug where DisablePrimitiveTypeConversion would cause property type annotations to be ignored in the new JSON format
- Fixes a bug where LoadProperty does not remove elements from a collection after deleting a link
- Fixes an issue where the URI Parser would not properly bind an action to a collection of entities
- Improves some error messages
The NuGet runtime in Visual Studio needs to be 2.0+ for Add Service Reference to work properly. If you are having issues with Add Service Reference in Visual Studio 2012, please ensure that NuGet is up-to-date.