Yes and no, at least not directly. There's a reference to the *Logging* assembly through the *common.dll*.
At the end of the day the problem is that any assemblies that are referenced by strong name in your configuration file should be added to the GAC, at least this is my experience when writing add-ins for Visual Studio 2008. In all other cases where I use
the EntLib for custom applications and web sites I never ran into this problem. It seems to be that there's something in the way add-ins are handled.
To provide more information, I am also not deploying my add-in in the typical C:\Users\<username>\Documents\Visual Studio 2008\Addins (Windows 7). I only place the .Addin file there but deploy the assembly elsewhere. So, I don't know if this adds
to the problem.
In any case, I managed to get it all working by making sure that all referenced assemblies in the configuration file are registered in the GAC. That does the trick. So, if anyone is having a similar problem just make sure you review your configuration