ArcGIS Pro 3.7 is now available, and with it, a headline milestone for SDK developers: the transition to .NET 10, Microsoft’s latest Long Term Support (LTS) release. The good news is that this is a minor (3.x) release — your existing add-ins built for Pro 3.0–3.6 will continue to run on 3.7 without recompilation.
If you do want to upgrade your development environment to take advantage of new features, you’ll need Visual Studio 2026 version 18.3.2 or later. See What’s New for Developers: Migrating to .NET 10 with ArcGIS Pro 3.7 for a full walkthrough.
Beyond the runtime, 3.7 delivers targeted API improvements across eight areas: Knowledge Graph, 3D Analyst, Editing, Parcels, Map Authoring, Geodatabase, Utility Network, and the Framework. Here’s what’s new.
3D Analyst
Three additions at 3.7 expand what you can do programmatically with lidar and surface data.
LAS Class Code Editing. You can now edit LAS class codes directly through the API — useful for add-ins that implement classification workflows on point cloud data without leaving Pro.
Shape Interpolation Using Terrain Layers. Terrain layers can now serve as the surface source for shape interpolation, giving more flexibility in 3D geometry workflows where terrain-derived elevation is the authoritative surface reference.
Polygon to Multipatch Conversion. The SDK now supports converting polygon geometries to multipatches using both TIN and Terrain layers. This is a practical addition for 3D feature creation workflows where the surface defines the vertical extent of an extruded footprint.
For code snippets and samples, see the 3D Analyst Data Code Snippets on the GitHub wiki and the 3D Analyst Community Samples.
Editing
The editing API has been significantly enhanced at 3.7, particularly for coordinate geometry (COGO) and traverse workflows. A new ArcGIS.Desktop.Editing.COGO namespace brings comprehensive in-memory traverse support — including building, adjusting, and closure calculations — directly into add-in workflows.
In-Memory Traverse Building from COGO Measurements. You can now build traverses in-memory from COGO measurements to calculate closure error, perform adjustments, and create features — all without writing to disk mid-workflow. This makes it possible to integrate programmatic traverse computations cleanly into broader editing workflows.
Loading Traverse Courses into the Traverse Tool UI. Add-ins can now programmatically load traverse courses into the traverse tool interface, enabling pre-population from external data sources (such as imported survey files) and a clean handoff to the user for review or adjustment.
Parcels
Two geometry-level additions that make parcel boundary work more precise.
Geometry Simplification for Tangent Segments. A new simplification function lets you remove vertices that fall between tangent segments, cleaning up parcel geometry without introducing angular error at curve boundaries.
Circular Arc Parameter Calculations. New calculation functions expose circular arc parameters — radius, central angle, chord length, and related values — providing the foundational building blocks for parcel fabric workflows involving curved boundaries.
Map Authoring
Several incremental but useful additions for developers working with map configuration.
Programmatic Map Grid Settings. You can now update per-map grid settings and grid visibility through the API, removing the need for manual configuration of reference grids when building map-driven workflows.
Layer Editability Check Without Starting an Edit Session. The SDK now exposes the ability to check whether a layer is editable before an edit session is started. A practical quality-of-life improvement for add-ins that need to validate layer state before prompting users to begin editing.
Vertical Coordinate System Updates. The Coordinate System control has been updated to better support Vertical Coordinate Systems, extending programmatic coordinate system management to the vertical dimension.
Geodatabase
Two additions that improve how add-ins interact with versioned geodatabases.
Post and Reconcile Extension Methods. New extension methods for Post and Reconcile operations are now available — and importantly, they support Pro’s Undo/Redo operation stack. This means these operations integrate cleanly into the existing edit session model, giving users the ability to roll back if needed.
Conflict Information for Traditional Versioning. Developers can now access conflict information for traditional versioning workflows through the API. This opens the door to building custom conflict-review experiences or surfacing versioning state directly within an add-in.
Utility Network
Telecommunications Domain Network Support. The SDK now includes support for a telecommunications domain network, enabling developers to model and manage telco assets and infrastructure within the Utility Network framework. This extends the existing electric, gas, and water domain support to cover telecom-specific asset types and connectivity rules — opening a new class of network management workflows for the Pro developer community.
Framework and Application
This release delivers several enhancements to extensibility, deployment, and table management.
Custom Toolbars for View Panes. Developers can now add custom toolbars to view panes, enabling context-specific toolsets that surface directly where users need them — rather than relying solely on the ribbon.
Add-In Side-by-Side Loading into a Named Custom Load Context. Building on the side-by-side isolation work from 3.6, this release adds support for loading add-ins into a named custom load context. This gives teams greater control over dependency scoping and isolation in complex deployment scenarios.
Table Control Enhancements. New command APIs and properties for TableControl and TableView enable add-ins to support field calculations, geometry calculations, row operations, and selection workflows programmatically. The AttachmentProperties API also gives you finer control over attachment metadata when adding or updating attachments in edit workflows.
Azure Add-In Signing — Updates and Bug Fixes. The Azure Key Vault-based digital signing workflow has received targeted updates, improvements, and bug fixes at 3.7. If you ran into issues with this at 3.6, it’s worth revisiting.
Knowledge Graph
The Knowledge Graph API has expanded significantly at 3.7, with notable additions to both Link Chart editing and Investigation-level configuration management.
Link Chart Content Editing. You can now programmatically add, update, and remove content within Link Charts, giving add-ins full control over the visual investigation layer — not just the underlying data.
Stored Query and FFP Configuration Management. The Investigation API has been extended to access, add, update, and remove stored query definitions and stored Filtered Find Path (FFP) configurations. This enables add-ins to manage the analytical building blocks of an investigation without relying on the UI.
FFP Configuration Import/Export. Developers can now import and export FFP configurations through the API, making it straightforward to package, share, and deploy investigation templates across environments.
File-Based Knowledge Graphs. At 3.7, the SDK adds support for creating and connecting to file-based Knowledge Graphs — a more lightweight alternative to enterprise-backed graph stores, and a useful addition for local development and testing workflows.
For a full reference on the Knowledge Graph API, see the ProConcepts: Knowledge Graph documentation.
Get Started with ArcGIS Pro 3.7
ArcGIS Pro 3.7 and the updated SDK are available now.
- Explore: Review the What’s New for Developers at 3.7 section in the API Reference for the full list of changes at this release.
- Download: Get the ArcGIS Pro SDK 3.7 from the Visual Studio Marketplace and follow the Installation and Upgrade ProGuide to update your environment.
- Reference: Browse the updated ProConcepts and ProGuide documentation for patterns around the new APIs, and check out the Community Samples for working code examples.
- Engage: Share feedback and what you’re building on the ArcGIS Pro SDK Esri Community.
As always, we’re interested in how these updates are being used in real-world workflows.
Article Discussion: