If your company decides to sign their Enterprise Library files with their public and private keys the default Ent LIb Configuration tool that is integrated with Visual Studio will not by default use the newly signed assemblies. The following is a brief description on how to update your system so that the appropriate assemblies are used.
1.) Add the following registry key and values to the registry
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\Packages\{488366a4-630c-4a0e-a6a2-b019cee13bea}\{ConfigurationSets} You need to add an additional configuration set. By default you will see the Microsoft Signed set. Below is how the new key will be set up. In the following example you will need to change the paths for ConfigurationUIAssemblyPath and ConfigurationUIPluginDirectory to point to where your company signed assemblies are located.
{Your Set Name} (Default) REG_SZ (Value not set) (ConfigurationUIAdapterClass) REG_SZ Microsoft.Practices.EnterpriseLibrary.Configuration.Design.UI.SingleHierarchyConfigurationUIHostAdapter (ConfigurationUIAssemblyPath) REG_SZ C:\CompanySigned\GAC\EnterpriseLibrary\Microsoft.Practices.EnterpriseLibrary.Configuration.Design.UI.dll (ConfigurationUIPluginDirectory) REG_SZ C:\CompanySigned\GAC\EnterpriseLibraryhttp://entlib.codeplex.com/Thread/View.aspx?ThreadId=30986http://blogs.msdn.com/b/tomholl/archive/2007/04/19/avoiding-configuration-pitfalls-with-incompatible-copies-of-enterprise-library.aspx
