Arcgis Vba Compatibility

[Rocki Eibl]

BackgroundAs with many of us, my organization is using both ArcMap (10.8.1) and ArcGIS Pro (2.9). Our Enterprise GIS is at 10.9.1. After reading about the changes in ArcGIS Pro 3.x, we have been hesitant to upgrade beyond 2.9. Some of our users are effectively stuck with ArcMap for now (waiting on 3rd party add-ons to upgrade). We need to maintain functionality of being able to edit and work with enterprise geodatabases from both ArcMap and ArcGIS Pro. However, there are also some business cases that could benefit from the upgrade to ArcGIS Pro 3.x. So... we are sort of in a pickle at the moment.

Per this compatibility matrix, you should keep the geodatabase (SDE) at version 10.8.1.x to remain compatible with both ArcMap 10.8.1 and ArcGIS Pro 2.6. Note that ArcGIS Enterprise 10.9.1 is the last (most compatible) version with ArcMap 10.8.2 (last release). Starting at ArcGIS 11.0, many ArcMap dependent features are deprecated.

Also, note that the compatibility matrix suggests staying at ArcGIS Pro 2.9 (if continuing to use ArcMap). I have seen users, editing with compatible version of ArcGIS Pro (say Pro 2.9); they may use later version for read-only functions, analysis, search, query (say Pro 3.1). You will quickly realize being in unsupported/incompatible versions for Desktop (ArcMap and Pro), Enterprise and Geodatabase. It becomes a huge issue for IT/GIS admins to maintain a mixed environment with limitations on upgrades, service packs, security patches. You may continue to operate mixed desktop apps, as long as there are no issues. But this not a best practice and does not align with ArcGIS implementation architecture patterns.

There are many enhancements in ArcGIS including geodatabase objects created by ArcGIS Pro. Solutions like ArcGIS Utility Network, Trace Network, Parcel Fabric, Pipeline Referencing are developed for ArcGIS Pro and comprise of GDB objects that can only be read by ArcGIS Pro. GDB functions like Attribute Rules, Contingent Values are specific to ArcGIS Pro.

We have similar issues where I work regarding third party add-ons that only work with ArcMap 10.6.1, etc. For those users, we kind of forced them to learn Pro but still use ArcMap when needing that add-on. Maybe it's time to have people live in both worlds until it's "time".

Thanks to everyone for your replies. I really appreciate it. The compatibility matrix is most useful. This aligns with what I have read so far that you start encountering issues at Pro 3+ unless your entire organization is already migrated off ArcMap and using Enterprise 11.

After a recent upgrade of ArcPro (to v 3.1.0) I am now seeing this notation in FME Desktop and FME Server logs....Current installed ArcGISPro version '3.1.0' is unsupported. Minimum supported version is '2.3.0', and maximum supported version is '3.0.0'....what does this mean exactly?...do I need to upgrade FME?...on Desktop it doesnt seem to make a difference (I can still successfully run operations), but now some Scheduled Services are failing in FME Server and I am wondering if this is the reason. Thank you

ArcGIS Pro 3.1.0 needs FME 2022.2.4. as can be read in Notes on FME and Esri Versions and Compatibility. Always check before upgrading as this may break the compatibility as you experienced. Especially as ArcGIS Pro is not backwards compatible as far as I know.

In ArcGIS Pro, under settings --> about, you can disable the checkbox "Check for updates on startup" to prevent the notification to show every time a new version is available. I did this because I can't keep up with the ArcGIS Pro update cycle speed in the production environment.

This topic discusses the extension compatibility with different versions of ArcGIS Enterprise and how to upgrade an older version of SOE or SOI project to be built with a later version of ArcGIS Enterprise SDK.

The best practice to deploy extensions to different versions of ArcGIS Enterprise is to compile the extension using the same version of ArcGIS Enterprise SDK as the version of ArcGIS Server where the extension will be deployed. Since how ArcGIS Server works with older versions of extensions is different depending on its version, this section explains the extension compatibility with different versions of ArcGIS Server.

Starting with ArcGIS Server 11.0, deploying SOEs or SOIs built with ArcGIS Enterprise SDK 10.x is no longer supported. In ArcGIS Server 11.0, if you register an SOE or SOI built with the 10.x version of ArcGIS Enterprise SDK, you will see the following error:

To continue using the extension in ArcGIS Server 11.0, you need to upgrade your extension and build it with ArcGIS Enterprise SDK 11.0. The extension upgrade process requires development efforts. Follow the instructions in Migrate older .NET SOE or SOI projects to 11.

Deploying an older version of SOE or SOI to ArcGIS Server at 10.9.1 or earlier version is not supported. Even though the extension may still load and function properly in the newer version of ArcGIS Server, the best practice is to recompile the extension using the same version of ArcGIS Enterprise SDK as the version of ArcGIS Server where the extension will be deployed. With that being said, if you want to deploy your SOE or SOI to a specific version of ArcGIS Server, you should compile your SOE or SOI using the same version of ArcGIS Enterprise SDK.

To upgrade your ArcGIS Enterprise SDK, you should first uninstall any previous version of ArcGIS Enterprise SDK. This can be done through the Control Panel for Windows. Then, you should set up the development environment and install the later version of ArcGIS Enterprise SDK you need. Depending on the version of Enterprise SDK you installed, you can either recompile your older version of the SOE or SOI project or migrate your project.

Double-click your project in Solution Explorer to open and edit the project's .csproj file. Change the AddInTargetVersion to match your SDK version and save this file.For example, if you upgrade to Enterprise SDK 10.9 or Enterprise SDK 10.9.1, set it to nargetersion10.9dnargetersion.

Sometimes Visual Studio may complain that the .soe file already exists in the bin\Debug or obj folder and can't be deleted when rebuilding the project. If this happens, you can manually delete these folders and then rebuild the project.

LinkedIn and 3rd parties use essential and non-essential cookies to provide, secure, analyze and improve our Services, and to show you relevant ads (including professional and job ads) on and off LinkedIn. Learn more in our Cookie Policy.

As the introduction to that article notes, FME supports a variety of licensed, installed versions of Esri ArcMap and Esri ArcGIS Pro applications. So, how do you set up FME for your required Esri product? And what happens if your system has both Esri ArcMap and Esri ArcGIS Pro installed and licensed?

The other wrinkle, of course, is that Python compatibility is also woven into how FME uses Esri products. For example, if you selected ArcMap compatibility, but an Esri ArcGIS Python interpreter, you'd get an error like this:

So please do check into these events and support our partners in their excellent work. I suspect some events will be broadcast online and so would be accessible even if you don't live in the region. There is always a lot of great information about the latest FME functionality and the latest user stories.

Back in New Zealand, Oxfam Trailwalker is a fundraising event that involves teams competing in long-distance trail walks. Gary Nicholson from Locus frequently volunteers his organizational skills and makes use of FME to do so.

FME Community members, please join me in welcoming these folks to Safe, and I'm sure they'd appreciate a follow on LinkedIn. They have public-facing roles, so I am sure you will interact with them all at some point anyway.

If you would like to join them, Safe often has career openings available. Right now, I see roles in software development for Server, a C++ developer for the FME engine, technical support for FME Server, marketing, admin assistant, and account managers.

3a8082e126