Load behavior for Referenced DLLs in Add-ins

[lmc.engineering]

Hi All,

Let's say I have two add-in applications that I've built, A & B, with both making reference to a specific Class library DLL (C). When I build each Add-in they both produce a local copy of the DLL file (C) , however when Inventor loads, am I right in saying that Inventor only loads the first instance of C when loading the Add-ins? 

As it stands, if I am attempting a debug of B (through launch of Inventor.exe) , and  A is already built (sat within the ApplicationPlugins folder), during the launch of Inventor, C is being loaded via Addin A as it's the first instance found, and therefore any changes I made to C for debugging B are not present, due to Inventor referencing an older version of C, through A.

I understand  when I actually come to use the Add-in I will need to re-build all addins that reference this DLL, however, is it really the case that I need remove all other copies of this DLL from the ApplicationPlugins folder if I attempt to use a version that differs, even for a debug? .. I mean it seems that's the logical conclusion, I just wonder if others have a different method when this kind of thing arises?

Thanks

[nmunro · Accepted solution]

For debugging purposes are you not able to disable your A add-in? You could do that via Tools > Add-ins, or just rename the file extension of the Axxx.addin file in the ApplicationPlugIns folder. Inventor loads add-ins in order based on the GUID for the add-in so changing the load order is possible but a bunch more work.

[lmc.engineering]

Thanks nmunro,

I think ultimately disabling the addins before debug is going to be the solution here. I don't know why I couldn't see that solution...

Good to know how Inventor is loading the Addins.

Regards