If I have multiple add-ins that are all using the same DLL but each add-in is using a different version of the DLL, it seems as though only one version of the DLL is loaded into ArcGIS Pro. This causes pro to crash when the add-in using a later version of the DLL tries to call a function that doesn't exist in an earlier version. Is there a way to prevent this from happening and make sure Pro is loading in the DLLs separately for each add-in? This seems to have been possible in ArcMap and updating the DLLs all to the same version will not be an option as this creates more work every time a new add-in is created to have to go in and update every add-in using the DLL to work with the latest version.
Only strong named assemblies are versioned in .NET. If your shared assembly is unsigned, as far as .NET is concerned its version is, effectively, 0.0.0.0. To strong name your assembly you will have to sign it.
Only strong named assemblies are versioned in .NET. If your shared assembly is unsigned, as far as .NET is concerned its version is, effectively, 0.0.0.0. To strong name your assembly you will have to sign it.
