Add-ins that share same custom library

Discussion created by rcoodey on May 6, 2011
Latest reply on May 24, 2011 by rcoodey
We have some standard library projects that are shared among multiple different add-in projects.  As I have been bouncing back and forth getting these different add-ins ready to go into production, I realized that when I would make a change to one of the libraries, and then recompile a specific add-in, it would crash at runtime saying it couldn???t find the method or something of that nature.  It seems that it is using the DLL from another add-in it has loaded already.

1) Is there a way to tell it to use the DLL that is bundled within its own add-in?
2) If I increment the build version number on each DLL with each test deploy will it then use the right one? This doesn't seem to work :(

Is there any easy way to not have to re-deploy all our add-ins when just wanting to update one with a small tweak/update in a shared dll? 

Thanks a lot for any info.