Signing Enterprise Library 4.1 with our company key

Topics: Building and extending application blocks
Oct 14, 2009 at 3:20 PM
Edited Oct 14, 2009 at 3:27 PM

I opened the Enterprise Library solution and delay signed each project.  Things compiled well.  I was then able to complete the signing of all assemblies with the private key.  The assemblies were located in the Enterprise Library / bin directory. There are a few other dll's in the directory i.e. ObjectBuilder2.dll, Unity.dll etc. (these assemblies are also in the Lib directory).

1.) Do I also need to sign these assemblies with our company key? (If yes, where can I find the source code for these assemblies?)

2.) I tried to use the assemblies by adding to a project.  I get the following error that I am trying to resolve. 

An error occurred creating the configuration section handler for loggingConfiguration: Could not load file or assembly 'Microsoft.Practices.EnterpriseLibrary.Logging, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)





Oct 14, 2009 at 3:59 PM

I believe I resolved #2

I used the enterprise library configuration tool and it inserted the incorrect values in the config file.  I updated with the appropriate public key and this solves #2 had more information regarding this.

Oct 14, 2009 at 11:16 PM

The source code for Unity and ObjectBuilder2 are available as part of the standalone Unity download (