I have an add-in that uses Gdal (c# bindings) which works in ArcGIS Pro 3.3, 3.4, and 3.5, but after upgrading to 3.6, I run into a conflict when registering Gdal, I assume due to a Gdal change in Pro. So now I'm going to have to changes versions of Gdal in my add-in to fix this issue, and I really don't want to have to do this. Does anyone know a solution to this? It's very aggravating! I've had this happen before with earlier versions of Pro and Gdal and with log4net in Pro. This issue has come up before and supposedly ESRI is working on a solution: https://community.esri.com/t5/arcgis-pro-sdk-ideas/implement-assemblyloadcontext-for-add-in-isolation/idi-p/1589344/jump-to/first-unread-message
Has there been any progress on this???
https://github.com/esri/arcgis-pro-sdk/wiki/ProConcepts-Advanced-Topics#side-by-side-loading-to-resolve-addin-dependencies
you will probably want to load your addin side-by-side
Thanks for letting me know about this. I tried it but I'm still having issues.
Please refer to https://community.esri.com/t5/arcgis-pro-sdk-questions/gdal-conflict-in-pro-3-6-part-2/m-p/1679153#M13395 for the latest update
FYI, If you're using the ESRI nuget package from the previous message and are getting the PINVOKE error that gdal_wrap is missing, make sure that the <RuntimeIdentifier> setting in your .csproj file is set to win-x64 NOT win10-x64.
You're welcome.
Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
