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???
