Create a Local Server deployment

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.

ArcGIS Runtime components

The ArcGIS Runtime components available to include in your Local Server deployment are described in the following table. In the ArcGIS Runtime Local Server Deployment Builder utility the following Deployable Components are available for both ArcGIS Pro and ArcMap Local Servers.

Deployable Component	Description
Local Server (Pro, ArcMap)	Required if your application uses any local services. This is enabled by default when you initially add the Local Server package to your project.
Microsoft C and C++ Runtime Libraries (ProCRuntime, ArcMapCRuntime)	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.
Geoprocessing (ProGeoprocessing, ArcMapGeoprocessing) Available child packages 3D Analyst extension (Pro3DAnalyst, ArcMap3DAnalyst): Required for any geoprocessing packages that make use of 3D Analyst tools. Geocoding (ProGeocoding, ArcMapGeocoding): Provides the ability to use ArcGIS Locators. Map packaging (ProMapPackaging, ArcMapMapPackaging): Adds data consolidation, map packaging and create runtime content tools. Map Server Results (ProMapServerResults, ArcMapMapServerResults): Required to add geoprocessing results as map services. Network Analyst extension (ProNetworkAnalyst, ArcMapNetworkAnalyst): Required for any geoprocessing packages that make use of Network Analyst tools. Spatial Analyst extension (ProSpatialAnalyst, ArcMapSpatialAnalyst): Required for any geoprocessing packages that make use of Spatial Analyst tools.	Provides the ability to perform geoprocessing tasks via geoprocessing packages. For a list of supported tools, see Supported geoprocessing tools. You may need to also enable some of the available child packages to provide support for additional geoprocessing functionality, such as Network or 3D analysis.
Python Scripting (ProPythonScripting, ArcMapPythonScripting)	Provides the ability to use Python scripts.
Additional data formats (ProAdditionalDataFormats, ArcMapAdditionalDataFormats) Available child packages Raster (ProRaster, ArcMapRaster): Provides additional raster file data format support. For a list of supported rasters, see Raster file formats (ArcGIS Pro) or List of supported raster and image data formats (ArcMap). ECW Rasters (ProECWRasters, ArcMapECWRasters) Mosaic Rasters (ProMosaicRasters, ArcMapMosaicRasters) Vector (ProVector, ArcMapVector): Provides additional vector file data format support such as the ability to use shapefiles. SDE (ProSDE, ArcMapSDE): 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, IBM Db2, Informix, Microsoft SQL Server, Oracle, PostgreSQL, SAP HANA, SQLite, or Teradata (depending on your version of ArcGIS Pro or ArcMap). The drivers for the specified database must be present on the target machine.	Provides additional vector file data format and raster file data format support. Enable the appropriate child packages for the formats your app needs to support.
Additional projection engine transformations (ProAdditionalProjectionEngineTransformations, ArcMapAdditionalProjectionEngineTransformations)	Adds additional projections and geotransformations. For more information on coordinate systems, see Spatial references.
Debug (ProDebug, ArcMapDebug) Available child packages Logging (ProLogging, ArcMapLogging): Supports writing log messages from your running app.	Supports debugging of your deployed app. Should be used for testing only, and not included in your final app deployment.