API Reference and Documentation for previous releases

307
3
Jump to solution
02-03-2021 09:07 AM
DwayneKuykendall
New Contributor II

The Web page for the current version of the ArcGIS Runtime .Net API previously contained links to earlier versions.  It is critical to retain access to API documentation for previous releases.

Why were the links to these versions removed and how do we access the API Reference and Documentation for previous releases?

 

2 Solutions

Accepted Solutions
dotMorten_esri
Esri Frequent Contributor

We're currently working on adding a list of versions an API is supported in to the bottom of each API description, so you can see when a particular API was introduced. Would this be good enough, or do you only want to see APIs available in a specific version? (consider that maintaining multiple APIs is quite an overhead for us, and we frequently update, fix and improve doc on existing older APIs as well, so you'd likely not get the updated documentation in the older versions - only maintaining one means we have more resources to improve our documentation).

View solution in original post

0 Kudos
Thad
by
New Contributor

You can find the API reference (.chm) and developer guides (.pdf) for previous .NET versions in the download area of the site: https://developers.arcgis.com/downloads/#net

We don't currently have PDF versions of the developer guide for the current release, but are working on a way of providing that as offline content as well.

View solution in original post

3 Replies
dotMorten_esri
Esri Frequent Contributor

We're currently working on adding a list of versions an API is supported in to the bottom of each API description, so you can see when a particular API was introduced. Would this be good enough, or do you only want to see APIs available in a specific version? (consider that maintaining multiple APIs is quite an overhead for us, and we frequently update, fix and improve doc on existing older APIs as well, so you'd likely not get the updated documentation in the older versions - only maintaining one means we have more resources to improve our documentation).

View solution in original post

0 Kudos
DwayneKuykendall
New Contributor II

This is a good solution.  I agree that maintaining multiple documents is a challenge.  If all existing and previous API documentation is preserved and marked appropriately, it would be great.  Obsolete or deprecated functionality could be marked appropriately.  

It would be good also to have an option to filter the documentation to functionality that only exists in a certain version.

Thanks for the quick update!

Thad
by
New Contributor

You can find the API reference (.chm) and developer guides (.pdf) for previous .NET versions in the download area of the site: https://developers.arcgis.com/downloads/#net

We don't currently have PDF versions of the developer guide for the current release, but are working on a way of providing that as offline content as well.

View solution in original post