Local services allow you to deploy services that run locally with your app to provide functionality like geoprocessing, routing, and so on. In ArcGIS Runtime SDK for .NET, local services are only available for Windows Presentation Framework (WPF) apps. An app built for another ArcGIS Runtime for .NET platform can use such functionality from an online service, but not locally.
Deploying Local Server
The first time you build a project that uses Local Server, a deployment manifest file will be created in your project directory (ArcGISLocalServer.AGSDeployment).
The ArcGISLocalServer.AGSDeployment file is created in your project directory, but is not added to your Visual Studio project. To see it listed in the Solution Explorer window, you will need to choose to Show All Files.
<!--Provides the ability to use Python scripts.--> <Package name="Python Scripting" enabled="true"> <ChildPackages> <!--Provides support for Geoprocessing tools that use python--> <Package name="Python Geoprocessing tools" enabled="true" /> </ChildPackages> </Package>
Apart from installing the Local Server SDK and ensuring you have edited ArcGISLocalServer.AGSDeployment to include the components you need, there are no additional steps for deploying Local Server capabilities for your ArcGIS Runtime SDK for .NET app.
If you run local services based on map documents, and those map documents use third-party fonts, then you must make sure that those third-party fonts are installed on each client machine where those services will run. Otherwise, the corresponding local service may fail to start or may fail to render symbols that use those fonts.
ArcGIS Runtime components
The ArcGIS Runtime components available to include in your Local Server deployment are described in the following table.
Microsoft C and C++ Runtime Libraries
Including Microsoft C and C++ libraries in the runtime deployment allows for XCopy style deployments. Only include these if your setup is not installing the Microsoft redistribution package.
Required if your application uses any local services. This is enabled by default when you initially add the Local Server package to your project.
Provides the ability to perform geoprocessing tasks via geoprocessing packages. For a list of supported tools, see Supported geoprocessing tools.
3D Analyst extension
Required for any geoprocessing packages that make use of 3D Analyst tools.
Adds data consolidation, map packaging and create runtime content tools.
Map Server Results
Required to add geoprocessing results as map services.
Network Analyst extension
Required for any geoprocessing packages that make use of Network Analyst tools.
Spatial Analyst extension
Required for any geoprocessing packages that make use of Spatial Analyst tools.
Provides the ability to use Python scripts.
Python geoprocessing tools
Provides support for geoprocessing tools that use Python.
Additional data formats
Provides additional vector file data format and raster file data format support.
Provides additional raster file data format support. For a list of supported rasters, see Supported raster dataset file formats.
Provides support for ECW format raster.
Provides support for raster mosaic layers.
Provides additional vector file data format support such as the ability to use shapefiles.
Adds support to allow you to connect directly to enterprise geodatabases. This option must be selected in conjunction with at least one of the following DBMSs: Alitbase, Dameng, DB2, Informix, Netezza, Oracle, PostgreSQL, SAP HANA, SQL Server, SQLite, or Teradata. The drivers for the specified database must be present on the target machine.
Additional projection engine transformations
Adds additional projections and geotransformations. For more information on coordinate systems, see Spatial references.
Supports debugging of your deployed app. Should be used for testing only, and not included in your final app deployment.
Supports writing log messages from your running app.