ArcGIS Pro Add-Ins: Navigating ArcGIS Pro Upgrades

ArcGIS Pro Evolution 

ArcGIS Pro is a fantastic example of rapid software change. Version 1 was released on January 27, 2015, as the next generation desktop GIS to replace ArcMap; and ArcGIS Pro version 3.3 was just released in May 2024. In the GIS community, everyone had a unique reaction to opening ArcGIS Pro for the first time after using ArcMap. The redesign of the UI to use a ribbon that is dynamic and contextualized depending on which layer you have selected was perhaps the biggest source of confusion and consternation. For all its purported merits and intuitiveness, everyone felt some dismay as they struggled to locate common GIS functionality they could find in ArcMap within seconds. After the initial shock of using ArcGIS Pro wore off, it became easier to appreciate the new functionality that came along with subsequent version changes. 

Navigating the rapid evolution of software changes can be tricky and frustrating. Although upgrading software can bring new functionality, it can introduce potential risk from software bugs and may also make existing functionality obsolete, requiring you to update your workflows.  

Let’s walk through how software upgrades can impact your ArcGIS Pro Add-Ins, specifically. If you have invested in custom ArcGIS Pro Add-In development, you should pay particularly close attention to keep your Add-Ins from breaking. 

ArcGIS Pro Add-Ins 

ArcGIS Pro Add-Ins are developed using .NET and can be an excellent approach to extend and tailor Pro to your organization’s specific workflows by providing a custom tool or tools(s) populated on their own devoted tabs. They can increase productivity by programming repetitive workflows common to your organization. You can also entirely tailor how ArcGIS Pro boots up, with an Add-In variant called an ArcGIS Pro Configuration, allowing you to only include the default tabs, tools, etc. that are necessary for specific users, along with your custom tool(s). And since Add-Ins are developed in .NET, at the same version as the rest of ArcGIS Pro, upgrades to Pro may impact them.

Software Semantic Versioning 

Understanding software versioning rules can be a helpful first step for knowing how an upgrade to ArcGIS Pro may affect your ArcGIS Pro Add-In. ArcGIS Pro uses the software semantic versioning approach, which is a three-part version number to denote both functionality and the level of risk of implementing the change.  

Figure 1. Software semantic versioning consists of a number with three-parts: major, minor and patch. 

A major version change is a breaking change introducing a lot of new functionality and comes with the highest risk since it contains the greatest amount of code changes. A minor version change is non-breaking but introduces new functionality and comes with moderate risk with fewer code changes.  And a patch introduces no new functionality but resolves bugs and has the least amount of risk since the code is specifically targeting problems with existing code. Therefore, major version changes require the greatest amount of caution and patches require the least.  

Upgrading ArcGIS Pro Add-Ins 

Now that we’re on the same page when it comes to software semantic versioning, let’s take a closer look at ArcGIS Pro versions and how an upgrade may impact your ArcGIS Pro Add-Ins!  

Minor Version Changes 

If you have an ArcGIS Pro Add-In developed for ArcGIS Pro v2.x, you can upgrade to the latest version of the 2.x series (v 2.9.12 as of July 2024), and the original Add-In will continue to function.  

Similarly, if you have an ArcGIS Pro Add-In developed for ArcGIS Pro v3.x, you can upgrade to ArcGIS Pro v3.3.1 and the original Add-In will still work correctly.  Although ArcGIS Pro v3.0 – v3.2 uses .NET 6 and ArcGIS Pro v3.3 uses .NET 8 (Microsoft's latest version of .NET), .NET 8 is a non-breaking change, and the .NET 6 Add-In will continue to work fine in v3.3 (Table 1). 

Major Version Changes 

But what about an ArcGIS Pro Add-In originally developed for ArcGIS Pro 2.x? Will that continue to work fine in Pro 3.x? The short answer, no, no it will not...   

Since an upgrade from ArcGIS Pro 2.x to 3.x, is a major version change, it is a breaking change meaning that deprecated code will need to be resolved, and the Add-In must be recompiled targeting .NET 6.   

Furthermore, if you want to upgrade from v2.x to v3.3, but also want changes made to your Add-In, the code will first need to be first migrated from .NET Framework to .NET 6, fixing any breaking changes along the way and then recompiling against .NET 6. Next, it will need to be recompiled against .NET 8 – though there won’t be any breaking changes to fix, hurray! Finally, new .NET code could be written to address the requested changes for ArcGIS Pro v3.3. 

What about ArcMap Add-Ins?  

Recall what your initial impression of ArcGIS Pro was after using ArcMap after so many years – everything had moved to a ribbon; things were way --- way --- different!  Similarly, the ArcObjects code used to develop ArcMap Add-Ins is completely deprecated, meaning every bit of it would need to be rewritten for it to work in ArcGIS Pro. If this is something you need help with, our team can help rewrite your ArcMap Add-Ins or redevelop a new Add-In that matches your specifications. 

Add-In Experience 

To illustrate what an Add-In can do, here’s a few examples of Add-Ins we’ve developed for our clients.  

Multi-function ArcGIS Pro Toolbar – We developed a custom toolbar for a state transportation agency. The toolbar includes: 

• A dock pane with a collapsible, multi-level tree structure of data layers, allowing users to quickly add these layers to the Map tab's table of contents and manage content 

• Data layers and map templates which are controlled by a map service, providing GIS Administrators the ability to quickly update the toolbar 

• Zoom To tools for quick navigation to specific locations, such as coordinates, mile points, or bridges 

• Map tools for multiple functions, including opening Google Street View at a selected point, and loading a web page showing the last photograph captured at that mile point – and more! 

ArcGIS Pro Configuration – We created a tailored configuration for a city public works department, streamlining the ArcGIS Pro interface by removing unnecessary tabs and tools. The configuration retains essential default functionality while integrating custom tools allowing users to: 

• Create point features in bulk by parsing coordinates in various formats from a text file 

• Add individual points using a map tool 

• Delete points via another map tool 

• Access a customized editing environment 

ArcGIS Pro Toolbar for Definition Queries – We developed an Add-In for a construction management and inspection firm that efficiently applies definition queries to all layers within a group across multiple maps in a single ArcGIS Pro project. As users add or remove maps or group layers: 

• The Dock Pane dynamically updates to reflect these changes  

• The tree structure in the Dock Pane displays all maps in the project, along with their group layers 

• Users are able to easily input and apply queries to the desired layers 

Zoom To Coordinates – I started working on this Add-In to learn more about the functionality of ArcGIS Pro Add-Ins. Once the tool was built, we made it available as a free download from the ArcGIS Marketplace. Zoom To Coordinates: 

• Allows users to quickly navigate to specific coordinates on a 2D or 3D map in ArcGIS Pro 

• Allows users to optionally create graphics or overlays at the coordinates 

• Is highly customizable, with a variety of start-up and graphic-related options 

Summary 

Dymaptic is an innovative, woman-owned GIS service provider, offering consulting services, software development, and off-the-shelf software. We specialize in developing Add-Ins to customize functionality in ArcGIS Pro, leveraging our expertise in both GIS and .NET. Contact us if you need to upgrade an Add-In for the latest version of ArcGIS Pro or if you want to discuss your ideas for a remarkable Add-In.