You can deploy Local Server for apps developed using either .NET Framework or .NET 8 for Windows. Local Server is not supported for apps developed using UWP or .NET for iOS, Android, and Mac Catalyst.
Build a Local Server deployment
For your application to use Local Server functionality you must create a Local Server deployment to include along with your application. The ArcGIS Maps SDK for Local Server installation includes all the components of Local Server. From the SDK installation you will create a deployment that includes only the components your application requires, reducing the footprint of your application.
The first time you build an application project that references the Esri. NuGet package, a deployment manifest file is created on disk in your project directory. This file is named ArcGIS where x represents the minor version of Esri. NuGet package.
The deployment manifest file is an XML-formatted text file that defines the components (listed as Package elements) of Local Server to deploy for your application. The top-level Package element in the file provides the ability to read geoprocessing and map packages created with ArcGIS Pro. Under the parent element are Child elements that are required to enable specific functionality such as geoprocessing, Python scripting support, and additional data formats. By default, only the core ArcGIS Pro Local Server component is enabled which is sufficient to support local map and feature services that reference ArcGIS file data sources, such as File Geodatabase. To include additional capabilities, you can edit the file in Visual Studio or a text editor and enable features by changing enabled="false" to enabled="true". Only packages with an enabled value of true are included in the deployment.
<!--This local server has support for ArcGIS Pro gpkx and mpkx packages. It is 64 bit only-->
<Package id="Pro" name="ArcGIS Pro Compatible Server" enabled="true">When you build your project, the components you have enabled in ArcGISLocalServer_200.x.AGSDeployment will be copied to your project output folder under a folder named Local (where x represents the minor version of Local Server). This folder must be deployed along with your application.
Local Server components
| Deployment Component | Description |
|---|---|
ArcGIS Pro Compatible Server (Pro) | This is required if your application uses any local services. |
Microsoft C and C++ Runtime Libraries (Pro) | Including Microsoft VC++ libraries in the runtime deployment following the app-local pattern allows for X style deployments. Only include these if your setup is not installing the Microsoft Visual C++ redistributable packages. |
Geoprocessing (Pro)Available sub-packages:
| Provides the ability to perform geoprocessing tasks via geoprocessing packages. For a list of supported tools, refer to the Supported geoprocessing tools topic. |
Python Scripting (Pro) | Provides the ability to use Python scripts in geoprocessing or labeling. |
Additional Data Formats (Pro)Available sub-packages:
| Provides additional vector file data format and raster file data format support. Enable the appropriate packages for the formats your application needs to support. |
Additional Projection Engine Transformations (Pro) | Adds additional projections and geotransformations. For more information on coordinate systems, refer to the Spatial references topic. |
Debug (Pro)Available sub-packages:
| Supports debugging of your deployed app. Should be used for testing only, and not included in your final app deployment. |