Deploy your app

Applications built with ArcGIS Runtime SDK for WPF are self-contained. For example, they do not add keys to the registry. Deploying them can be as simple as copying and pasting your .exe files along with other dependent files to a different machine or device. Likewise, uninstalling can be as simple as deleting the files. The SDK lets you build and deploy self-contained, stand-alone applications or build and deploy capabilities into existing software.

Deployment steps

Follow the steps below to deploy an application using the ArcGIS Runtime SDK for WPF:

Steps:

1. Make sure you have received the licenses you need for the capabilities you included in the application. For details on which licenses are needed for which capabilities and how to acquire them, see License level capabilities.
2. Follow the steps in Authorize a deployment, to obtain license string(s) for your application then add the string(s) to your project, as described in license your application.
3. Prepare your application: compile your application, then place it and any associated resources, such as client files, packages and data inside the folder you intend to use as a deployment folder.For example, for WPF, you need your .exe file, ESRI.ArcGIS.Client.dll, and if using local services, ESRI.ArcGIS.Client.Local.dll.
4. Because every application requires a minimum set of arcgis runtime components, you must create an arcgis runtime deployment using the Deployment Builder as described below in Create a runtime deployment. This results in a folder named arcgisruntime10.2.5 which contains files required by your application. For applications using local services: if the .exe file is at the same level as the arcgisruntime10.2.5 folder, the application will use the local server contained in the arcgisruntime10.2.5 folder. You can confirm this in Windows Task Manager by checking the location of the RuntimeLocalServer.exe processes. Alternatively, the application code can specify an alternative location for the arcgisruntime folder.
5. The deployment folder now contains everything you need to deploy your application. To distribute and deploy your application, copy and paste the deployment folder onto each of your end-user's machines or devices. Each deployment folder can be self-contained and consists of the following:
   1. Your application ( .exe).
   2. Supporting libraries your application uses.
   3. Runtime components from step 4 in a folder named arcgisruntime10.2.5.
   4. Supporting files, such as data or packages for local use. When you package data for use with your application, a report is provided that tells you which runtime components the package requires. Use this report to determine which runtime components to select during the deployment process.
6. Test the application by running it from this location.

Create a runtime deployment

Because every application you deploy requires a minimum set of runtime components, you must create a runtime deployment using the Deployment Builder, as described in the following procedure. In this process, you also select optional components, which helps ensure you deploy only the runtime components you need, keeping your application footprint small. For a description of the optional components, see the Runtime functionality options described section.

When you have finished creating a runtime deployment, the components you need will reside in a single folder named arcgisruntime10.2.5, giving you an easy way to include the components with your application, data, and client library files.

Note the Deployment Builder does not collect/bundle:

• client library files (platform-specific libraries).
• Your application files.

Steps:

1. In Windows, click Start > Programs > ArcGIS> Runtime SDK 10.2.5 for WPF > Runtime Tools > Deployment Builder 10.2.5.

   The ArcGIS Runtime Deployment Builder appears.

2. Click the Create Configuration button.
3. In the Deployment Configuration dialog box, in the Name text box, type a name for the configuration you're creating, then click OK. Configurations you create can be used as templates for future configurations.
4. On the Create Deployment Configuration dialog box, in the Name text box, type a name for the deployment. Deployment Builder uses this name as the first part of the name of the folder it creates to store the runtime deployment.
5. In the Version text box, type a number for the version of the deployment you named in the previous step. Deployment Builder uses this version as the last part of the name of the folder it creates to store the runtime deployment. Once you've created at least one deployment, when you specify a different version for a deployment with the same name, Deployment Builder creates a new deployment folder for the new version.
6. In the Platform area, use the drop-down that corresponds to the deployment platform(s) for this deployment, for example, Windows 32-bit or 64-bit.
7. In the APIarea ensure you have WPF selected. Additional options will only be displayed if you have multiple ArcGIS Runtime SDKs installed.
8. In the Select Optional Functionality area, check the check boxes that correspond to the capabilities you have included in the application you are deploying. If you do not check any boxes, only the minimum required runtime components will be included, such as mapping functionality. When you package data in ArcGIS for Desktop for use with your application, the Prepare window displays information regarding which options to select in this step. For details on each functionality option, see the Runtime functionality options described section. You can also click an item in the dialog box to view a brief description of it.
9. When you have finished selecting options, click OK to close the dialog box.
10. In the ArcGIS Runtime Deployment Builder dialog, the deployment name and version you just specified will be selected. Click the Generate button to create a deployment for it.
11. In the Deployment Location dialog box, type a path in the Folder text box or browse to an existing folder where you would like the Deployment Builder to write the runtime deployment. You will be prompted to choose whether to overwrite a previous deployment if the specified folder already contains a deployment and you are using the same deployment name (step 4) and the same version (step 5).
12. Click OK.

    The Deployment Builder writes the required runtime components and optional applicable runtime components to the folder ('arcgisruntime10.2.5') in the location you specified and displays a summary dialog box that provides details on the files copied. Now you are ready to deploy it, along with your application files (for example, your .exe file, client .dll files, and any local data it requires). To deploy the ArcGIS Runtime, place the arcgisruntime10.2.5 folder alongsdide your application exe. Alternatively you can place the arcgisruntime10.2.5 folder elsewhere on the target machine and set the InstallPath property of the ArcGISRuntime class to the folder containing the deployment. This must be done before calling the Initialize method.

Runtime functionality options described

When you package data for use with your application, a report is provided that helps you identify which options the package requires. The options are listed in the following table:

Option	Description
Local Server	Required if your application uses any local services.
Geocoding	Adds the ability to perform local geocoding. Requires your deployed application to be provisioned with a locator package.
Geoprocessing	Provides the ability to perform geoprocessing tasks via geoprocessing packages. For a list of supported tools, see Supported geoprocessing tools.
Spatial Analyst extension	Required for any geoprocessing packages which make use of Spatial Analyst tools.
3D Analyst extension	Required for any geoprocessing packages which make use of 3D Analyst tools.
Network Analyst extension	Required for any geoprocessing packages which make use of Network Analyst tools.
Map Server Results	Required to add geoprocessing results as map services.
Python Scripting	Provides the ability to use Python scripts.
Python geoprocessing tools	Provides support for geoprocessing tools that use python.
Python PDF output support	Provides support for tools that output PDF files.
Additional data formats	Provides additional vector file data format and raster file data format support.
Vector	Provides additional vector file data format support such as the ability to use shapefiles.
Raster	Provides additional raster file data format support. For a list of supported rasters, see Supported raster types.
Mosaic Rasters	Provides support for Raster Mosiac Layers.
ECW Rasters	Provides support for ECW format Raster.
SDE	Adds support to let you connect directly to enterprise geodatabases. This option must be selected in conjunction with at least one of the following DBMS(s): DB2, Informix, Oracle, PostgresSQL, or SQL Server.
Additional projection engine transformations	Adds additional projections and geotransformations. For more information on coordinate systems, see Coordinate system identifiers.
GPS	Adds support for using location information form a GPS receiver (a NMEA 0183 source) connected through a serial port or replayed from a file.
Advanced Symbology	Supports the handling of advanced symbology with complex renders.
Military Message Processing (MIL2525C)	Supports the handling and display of military messages using a MIL-STD-2525C-based symbol dictionary.
Military Message Processing (App6B)	Supports the handling and display of military messages using an App6B symbol dictionary.
S57 Hydrographic Symbology	Supports the handling and display of S57 data.