GitHub API missing for Pro 3.2 (for ESRI staff)

Vidar

I need to work on a legacy version of - specifically version 3.2 - however it seems to be missing - other older versions are working, but of course, the version I need is not.

Can anyone at ESRI help please.

GKmieliauskas

Hi,

What do you want to do with references from GitHub?

You can use latest ArcGIS Pro SKD reference. Make search for your interest and then switch to version you want.

Getech_Admin

test

Vidar

Well, yes fine, but should it really be missing in the first place, doesn't look great. Secondly - I'm trying to locate the correct version of the API for my custom instructions for use with CoPilot in Visual Studio - I didn't really feel comfortable with referenceing 3.6 API for AI based solutions/answers against a 3.2 version of Pro.

Thanks.

SelimDissem

Can you use Esri/arcgis-pro-sdk at v3.2.0.49743?

You can point CoPilot to the examples for 3.2 (arcgis-pro-sdk/Examples at v3.2.0.49743 · Esri/arcgis-pro-sdk)

Vidar

I could use the examples for now, but it would be good if you could fix it up eventually so the API is exposed again.

SelimDissem

this one: ArcGIS Pro 3.2 API Reference Guide?

Vidar

its not the same as the same kind of one/right format that is recommended here: https://github.com/Esri/arcgis-pro-sdk/wiki/ProConcepts-develop-addins-with-copilot

Scroll down to the custom instructions part of the page - also worth nothing that a lot of the instructions in that page are either out of date or just don't work as well.

SelimDissem

The References folder was added at 3.6 and doesn't exist in any of the previous versions. That folder contains a merge of the API documentation (XML in your Pro installation bin folder) and the Examples source code so using the examples directly should get you what you want/need.

If you use the master branch (a.k.a. latest), Copilot might on occasion provide suggestions for an API method/property/class added after release 3.2 and you will consequently get compile errors that have to be corrected manually.

RichardDaniels

Recall that Pro 3.2 introduced a new version of .Net Framework for Desktop, ensure you have the required version loaded prior to installing Pro 3.2