Our add-in uses Log4Net for logging. We're using an old version and there hasn't been any reason to change that. We've recently encountered an issue where one of our customers is using an add-in from another company and this add-in also uses Log4Net, but a newer version. Now when our add-in is activated by clicking the tab, a Log4Net error occurs. I'm able to reproduce this error by creating a test add-in using the newer Log4Net version. It seems very strange that a 3rd party library used by another add-in should have any effect on an unrelated add-in using a different version of the same same 3rd party library. Has anyone else encountered something like this? An ideas on how to fix this? I know we can update the Log4Net version, but that won't necessarily keep this from happening again.
