<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>idea Implement AssemblyLoadContext for Add-In Isolation in ArcGIS Pro SDK in ArcGIS Pro SDK Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-sdk-ideas/implement-assemblyloadcontext-for-add-in-isolation/idi-p/1589344</link>
    <description>&lt;P&gt;&lt;SPAN&gt;We would like to request the implementation of &lt;/SPAN&gt;&lt;SPAN&gt;AssemblyLoadContext&lt;/SPAN&gt;&lt;SPAN&gt; in ArcGIS Pro to improve add-in isolation and prevent assembly version conflicts.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Currently, ArcGIS Pro loads all add-ins into the same AppDomain, which means that when different add-ins depend on different versions of the same third-party library (like Log4Net or Gdal), only the highest version is loaded and used globally. This behavior often causes versioning conflicts and runtime errors when activating add-ins that expect a different version of the library.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The lack of assembly isolation becomes particularly problematic in .NET 5+ because, unlike the .NET Framework, it does not support side-by-side loading of different assembly versions in the same AppDomain. This results in unpredictable behavior and compatibility issues for developers building add-ins for ArcGIS Pro.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;By implementing &lt;/SPAN&gt;&lt;SPAN&gt;AssemblyLoadContext&lt;/SPAN&gt;&lt;SPAN&gt;, introduced in .NET Core, ArcGIS Pro could load each add-in in its own isolated context. This would allow add-ins to load and use their required library versions independently, without interfering with other add-ins. As a result, the stability and compatibility of add-ins would greatly improve.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;We believe this enhancement would resolve the ongoing versioning conflicts and prevent similar issues with other third-party libraries in the future. It would also align ArcGIS Pro with modern .NET practices for assembly management and dependency isolation.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;We appreciate your consideration of this request and look forward to seeing potential improvements in this area.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thank you, Johannes Strahler, IP SYSCON&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 26 Feb 2025 09:15:34 GMT</pubDate>
    <dc:creator>Johannes_Strahler</dc:creator>
    <dc:date>2025-02-26T09:15:34Z</dc:date>
    <item>
      <title>Implement AssemblyLoadContext for Add-In Isolation in ArcGIS Pro SDK</title>
      <link>https://community.esri.com/t5/arcgis-pro-sdk-ideas/implement-assemblyloadcontext-for-add-in-isolation/idi-p/1589344</link>
      <description>&lt;P&gt;&lt;SPAN&gt;We would like to request the implementation of &lt;/SPAN&gt;&lt;SPAN&gt;AssemblyLoadContext&lt;/SPAN&gt;&lt;SPAN&gt; in ArcGIS Pro to improve add-in isolation and prevent assembly version conflicts.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Currently, ArcGIS Pro loads all add-ins into the same AppDomain, which means that when different add-ins depend on different versions of the same third-party library (like Log4Net or Gdal), only the highest version is loaded and used globally. This behavior often causes versioning conflicts and runtime errors when activating add-ins that expect a different version of the library.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The lack of assembly isolation becomes particularly problematic in .NET 5+ because, unlike the .NET Framework, it does not support side-by-side loading of different assembly versions in the same AppDomain. This results in unpredictable behavior and compatibility issues for developers building add-ins for ArcGIS Pro.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;By implementing &lt;/SPAN&gt;&lt;SPAN&gt;AssemblyLoadContext&lt;/SPAN&gt;&lt;SPAN&gt;, introduced in .NET Core, ArcGIS Pro could load each add-in in its own isolated context. This would allow add-ins to load and use their required library versions independently, without interfering with other add-ins. As a result, the stability and compatibility of add-ins would greatly improve.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;We believe this enhancement would resolve the ongoing versioning conflicts and prevent similar issues with other third-party libraries in the future. It would also align ArcGIS Pro with modern .NET practices for assembly management and dependency isolation.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;We appreciate your consideration of this request and look forward to seeing potential improvements in this area.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thank you, Johannes Strahler, IP SYSCON&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Feb 2025 09:15:34 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-sdk-ideas/implement-assemblyloadcontext-for-add-in-isolation/idi-p/1589344</guid>
      <dc:creator>Johannes_Strahler</dc:creator>
      <dc:date>2025-02-26T09:15:34Z</dc:date>
    </item>
    <item>
      <title>Re: Implement AssemblyLoadContext for Add-In Isolation in ArcGIS Pro SDK</title>
      <link>https://community.esri.com/t5/arcgis-pro-sdk-ideas/implement-assemblyloadcontext-for-add-in-isolation/idc-p/1593180#M161</link>
      <description>&lt;P&gt;Check out this thread.&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.esri.com/t5/arcgis-pro-sdk-ideas/load-arcgis-pro-add-ins-into-their-own/idi-p/1477236#U1477236" target="_blank"&gt;https://community.esri.com/t5/arcgis-pro-sdk-ideas/load-arcgis-pro-add-ins-into-their-own/idi-p/1477236#U1477236&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Mar 2025 00:32:22 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-sdk-ideas/implement-assemblyloadcontext-for-add-in-isolation/idc-p/1593180#M161</guid>
      <dc:creator>vanesch</dc:creator>
      <dc:date>2025-03-07T00:32:22Z</dc:date>
    </item>
    <item>
      <title>Re: Implement AssemblyLoadContext for Add-In Isolation in ArcGIS Pro SDK</title>
      <link>https://community.esri.com/t5/arcgis-pro-sdk-ideas/implement-assemblyloadcontext-for-add-in-isolation/idc-p/1598741#M164</link>
      <description>&lt;P&gt;So technically, it sounds like different versions of &lt;A href="https://links.esri.com/webview2-download" target="_blank" rel="noopener"&gt;&lt;SPAN class=""&gt;Microsoft Edge&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;WebView2 Runtime&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;(e.g. if you built against a static vs. evergreen install on your development machine) could result in different behavior or unforeseen compatibility errors.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Mar 2025 20:02:18 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-sdk-ideas/implement-assemblyloadcontext-for-add-in-isolation/idc-p/1598741#M164</guid>
      <dc:creator>RichardDaniels</dc:creator>
      <dc:date>2025-03-24T20:02:18Z</dc:date>
    </item>
  </channel>
</rss>

