Select to view content in your preferred language

ArcGIS Runtime LocalServer 100.15 Deployment Issue

576
4
11-10-2022 01:59 AM
Danielb1
New Contributor

Hi All,

I'm creating a WPF app using ArcGIS Runtime 100.15 for .NET and ArcGIS Runtime Local Services 100.15 for loading and displaying local .mpkx files. After building the app, the build creates a ArcGIS Runtime 100.15 folder that contains 3 folders: client32, client64, and resources. It does not create the local server folder. In the Output tab in VS2022 when building the app, there is a line that writes: 

Processing LocalServer deployment...

LocalServer deployment processed. Found 0 files (0mb): 

I'm not sure why it's not creating the needed files for the local server and adding it to the build.

Any help would be much appreciated. Thank you.

Below is the contents of the "ArcGISLocalServer_100.15.AGSDeployment" file. We are using the local server only to load and display mpkx files, nothing else.

 

<?xml version="1.0" encoding="utf-8"?>
<!--ArcGIS Local Server Deployment Configuration-->
<Packages>
  <!--This local server has support for ArcGIS Pro mpkx and gpkx packages. It is 64 bit only-->
  <Package id="Pro" name="ArcGIS Pro Compatible Server" enabled="true">
    <ChildPackages>
      <!--Including Microsoft C and C++ libraries in the runtime deployment allows for XCopy style deployments on Windows.
Only include these if your setup is not installing the Microsoft redistribution package.-->
      <Package id="ProCRuntime" name="Microsoft C and C++ Runtime Libraries" enabled="false" />
      <!--Provides the ability to perform geoprocessing tasks via geoprocessing packages.-->
      <!--Geoprocessing packages must be created with ArcGIS Runtime support enabled.-->
      <Package id="ProGeoProcessing" name="Geoprocessing" enabled="false">
        <ChildPackages>
          <!--Adds 3D Analyst geoprocessing tools.-->
          <Package id="Pro3DAnalyst" name="3D Analyst" enabled="false" />
          <!--Provides the ability to use ArcGIS Locators-->
          <Package id="ProGeoCoding" name="Geocoding" enabled="false" />
          <!--Adds data consolidation, map packaging and create runtime content tools.-->
          <Package id="ProMapPackaging" name="Map Packaging" enabled="false" />
          <!--Adds the ability to produce results as Map Services.-->
          <Package id="ProMapServerResults" name="Map Server Results" enabled="false" />
          <!--Adds Network Analyst geoprocessing tools.-->
          <Package id="ProNetworkAnalyst" name="Network Analyst" enabled="false" />
          <!--Adds Spatial Analyst geoprocessing tools.-->
          <Package id="ProSpatialAnalyst" name="Spatial Analyst" enabled="false" />
        </ChildPackages>
      </Package>
      <!--Provides the ability to use Python scripts.-->
      <Package id="ProPythonScripting" name="Python Scripting" enabled="false" />
      <!--Provides additional vector and raster data format support.-->
      <Package id="ProAdditionalDataFormats" name="Additional Data Formats" enabled="false">
        <ChildPackages>
          <!--Provides additional raster file data format support.-->
          <Package id="ProRaster" name="Raster" enabled="false">
            <ChildPackages>
              <!--Provides support for Raster Mosaic Layers.-->
              <Package id="ProMosaicRasters" name="Mosaic Rasters" enabled="false" />
            </ChildPackages>
          </Package>
          <!--Provides additional vector file data format support.-->
          <Package id="ProVector" name="Vector" enabled="false" />
          <!--Adds support for direct connect to DBMS system that Esri supports. This option must be selected in conjunction with at least one of the following DBMS(s): DB2, Informix, Oracle, PostgreSQL, SQL Server, Netezza, HANA, Teradata or Alitbase.-->
          <!--SDE direct connect deployed. Specific database drivers also required.-->
          <Package id="ProSDE" name="SDE" enabled="false">
            <ChildPackages>
              <!--Adds support for direct connect to geodatabases stored in Dameng.-->
              <!--Dameng Drivers must be present on end users machine.-->
              <Package id="ProDameng" name="Dameng" enabled="false" />
              <!--Adds support for direct connect to geodatabases stored in DB2.-->
              <!--DB2 Drivers must be present on end users machine.-->
              <Package id="ProDB2" name="DB2" enabled="false" />
              <!-- Adds support for direct connect to geodatabases stored in Oracle.-->
              <!--Oracle Drivers must be present on end users machine.-->
              <Package id="ProOracle" name="Oracle" enabled="false" />
              <!--Adds support for direct connect to geodatabases stored in PostgreSQL.-->
              <!--PostgreSQL Drivers must be present on end users machine.-->
              <Package id="ProPostgreSQL" name="PostgreSQL" enabled="false" />
              <!--Adds support for direct connect to geodatabases stored in SAP HANA.-->
              <!--SAP HANA SQL Server Drivers must be present on end users machine.-->
              <Package id="ProSAPHANA" name="SAP HANA" enabled="false" />
              <!--Adds support for direct connect to geodatabases stored in SQL Server.-->
              <!--MS SQL Server Drivers must be present on end users machine.-->
              <Package id="ProSQLServer" name="SQL Server" enabled="false" />
              <!--Adds support for direct connect to geodatabases stored in SQL Server.-->
              <!--MS SQL Server Drivers must be present on end users machine.-->
              <Package id="ProSQLite" name="SQLite" enabled="false">
                <ChildPackages>
                  <!--Adds support for SpatiaLite geometry type-->
                  <Package id="ProSpatialLite" name="SpatiaLite" enabled="false" />
                </ChildPackages>
              </Package>
              <!--Adds support for direct connect to geodatabases stored in Teradata.-->
              <!--Teradata Drivers must be present on end users machine.-->
              <Package id="ProTeradata" name="Teradata" enabled="false" />
            </ChildPackages>
          </Package>
        </ChildPackages>
      </Package>
      <!--Adds more projections and geotransformations.-->
      <Package id="ProAdditionalProjectionEngineTransformations" name="Additional Projection Engine Transformations" enabled="false" />
      <!--Enables debugging options within the runtime.-->
      <!--Debugging options should only be used for testing purposes, and not deployed in final solutions.-->
      <Package id="ProDebug" name="Debug" enabled="false">
        <ChildPackages>
          <!--Adds support for runtime logging.-->
          <Package id="ProLogging" name="Logging" enabled="false" />
        </ChildPackages>
      </Package>
    </ChildPackages>
  </Package>
</Packages>

 

0 Kudos
4 Replies
MichaelBranscomb
Esri Frequent Contributor

Hi,

If you see the Client32/Client64 folders then I assume you are targeting .NET Framework with your WPF app (as opposed to .NET 6 or later).

By default you should see Local Server deployed under something like: `<YourAppProject>\bin\Debug|Release\net48\LocalServer100.15`.

 

Questions:

  • Are there any Errors or Warnings in the Error List? 
  • Is the Local Services NuGet package referenced from your application project or a class library project?
  • Where is the Local Server SDK installed on disk? (e.g. C:\Program Files\ArcGIS SDKs\LocalServer100.15)

 

0 Kudos
Danielb1
New Contributor

Hi Michael,

Thanks for the reply.

Correct, I am targeting .NET framework 4.8.

Local Server isn't deployed at all in my app project.

There are no errors or warnings regarding the local server.

The Local Services NuGet package is referenced from a class library project as well as the main application project.

The local server sdk is installed at: C:\Program Files\ArcGIS SDKs\LocalServer100.15.

 

I tried playing around with the manifest, adding and removing some features but nothing changes, it still says 0 files found when I build the project.

0 Kudos
PhilBastian
New Contributor II

Hi, I have just come across this exact same issue: .NET Framework 4.8 and LocalServer100.15 as per original post. Debug works fine since the SDK is installed, but I can't install the SDK on all production clients. Deployment instructions at https://developers.arcgis.com/net/local-server/deploy-local-server/ are for 200.x, but I assume they should hold for 100.x also, and there should be a LocalServer folder in the build output?

Was a solution to this found?

0 Kudos
PhilBastian
New Contributor II

...and because I posted the question I just found the answer.

The SDK installation has a "Local Server Deployment Builder" installed with it, which can create the required files. It's huge though!

Package

Size (Mb)

   

 

 ArcGIS Pro Compatible Server

 2002.5

 

2002.5 Mb

 

 

 Total Package Deployment Size

2002.5 Mb

 Compressed Size

720.9 Mb

0 Kudos