1. API enhancements
At 2.9 you can take advantage of API enhancements for:
Visual Studio Templates:- The Layout Tool item template creates a layout tool for adding/editing graphics in layout and map views and elements in layout.
- The Table Construction Tool item template creates a table construction tool for creating rows in standalone tables.
- Catalog pane enhancements for accessing GDB, file, and CAD data.
- API access to application options.
- Table templates, template commands, table editing, and sketch symbology customization.
- DDL support for annotation layers and mobile geodatabases.
- Add tables to group layers and layer documents (.lyrx), and save map to web map format.
- Table Control enhancements like “Go to” row, open + customize table pane/view.
- Support for retrieving and executing named trace configurations stored as part of a utility network.
- Traverse multiple levels of utility network associations in a single call (crucial for some utility network data models such as telecommunications).
A complete list of the API enhancements is provided in the API Changes section on this page.
2. .NET 6.0 and .NET Framework 4.8:
- ArcGIS Pro 2.9 is the last release with .NET Framework 4.8. ArcGIS Pro 3.0 will introduce support for .NET 6.0, Microsoft's latest edition of .NET. Support for .NET 6.0 will replace support for .NET Framework 4.8. With 3.0, .NET Framework 4.8 will no longer be supported. This will be a breaking change.
3.Visual Studio 2017, 2019, and 2022
- ArcGIS Pro 2.9 SDK is the last release with support for Visual Studio 2017 and 2019. ArcGIS Pro 3.0 SDK will introduce support for Visual Studio 2022, Microsoft's latest edition of its IDE. Support for Visual Studio 2022 will replace support for Visual Studio 2017 and 2019. With 3.0, Visual Studio 2017 and 2019 will no longer be supported.
4. ArcGIS Pro 2.5 and .NET Framework 4.8
As with the release of ArcGIS Pro 2.5, the minimum .NET target was switched to 4.8, and is no longer 4.6.1. What does this mean for you and your add-ins?- Existing add-ins, already deployed, will work at 2.9 with no change to their forward compatibility.
- Existing add-ins which are recompiled at 2.9 (e.g. because a code change was made) will also require the minimum target framework set to 4.8 or they will not compile. Note: As always, if an existing add-in is changed for any reason, the desktopVersion attribute in its Config.daml file should be changed to reflect the version of Pro it was last compiled against, in this case, now 2.9.
To migrate add-ins previously developed with 4.6.1 to 4.8, please consult technical support article How To: Convert a version 2.0 to 2.4 ArcGIS Pro SDK add-in solution to Pro 2.5 and later versions for more information
5. Target platform has changed from AnyCPU to x64
- When recompiling add-ins made with previous versions, it is recommended that you change the Platform Target in Visual Studio from "Any CPU" to "x64".
- Also starting at 2.8, when opening a user control .xaml using the Visual Studio Designer, it could result in the error "Could not load file or assembly 'ArcGIS.Desktop.Framework".
Please refer to the ArcGIS Pro SDK FAQ for more details.
6: SDK Resources
There are many ProConcepts, ProGuide, ProSnippets, and samples to help you get up and running with the new SDK features. Updates to the SDK Resources include, but are not limited to:- ProConcepts: Framework
- ProConcepts: COGO
- ProConcepts: Project Content and items
- ProConcepts: Editing
- ProConcepts: Layouts
- ProConcepts: Parcel Fabrics
- ProConcepts: Map Authoring
- ProConcepts: Reports
- ProConcepts: Geometry
- ProConcepts: Regressing Testing
- The Pro Community Samples and Snippets have new samples and snippets.