Ent Lib 3.1 assmeblies when re-complied and referenced in an application again, gives application compile errors

Topics: Building and extending application blocks, Caching Application Block , Cryptography Application Block, Data Access Application Block, Enterprise Library Core, Exception Handling Application Block, General discussion, Logging Application Block, Policy Injection Application Block, Security Application Block, Validation Application Block
Dec 4, 2007 at 5:07 PM
I am facing a strange problem, and seek your help.

I am using Ent Lib 3.1 in my application it works fine.

Now I did some change in Database.cs and re-complied the entire Ent Lib 3.1 using the BuildLibraryAndCopyAssemblies.bat.

When I reference the newly complied assemblies in my application, I get the following compile error. Can you help me understand why these assemblies are throwing this compile error when it worked perfectly fine when I referenced them earlier first time?

Please help me understand this trick.

CSC : error CS1577: Assembly generation failed -- Referenced assembly 'Microsoft
.Practices.EnterpriseLibrary.Caching' does not have a strong name
CSC : error CS1577: Assembly generation failed -- Referenced assembly 'Microsoft
.Practices.EnterpriseLibrary.Common' does not have a strong name
CSC : error CS1577: Assembly generation failed -- Referenced assembly 'Microsoft
.Practices.EnterpriseLibrary.Logging' does not have a strong name
CSC : error CS1577: Assembly generation failed -- Referenced assembly 'Microsoft
.Practices.EnterpriseLibrary.ExceptionHandling' does not have a strong name
CSC : error CS1577: Assembly generation failed -- Referenced assembly 'Microsoft
.Practices.EnterpriseLibrary.Security.Cryptography' does not have a strong name

Thanks in advance,
Nilesh
Dec 10, 2007 at 9:49 PM
Hi,

Your assemblies are signed. You were referencing signed assemblies so you could build just fine, but now you are referencing unsigned assemblies and the build fails.
Either sign the new entlib binaries you're building or avoid signing your own binaries.

Fernando