Help with strong naming .net dlls

[fahd]

Hi,

I am trying to use a particular dll bought from a company that has a
strong name. As a consequence had to give a strong name to all the
dlls involved in the project. Im also using the following microsoft
application block dlls

Microsoft.Practices.EnterpriseLibrary.Caching.dll
Microsoft.Practices.EnterpriseLibrary.Common.dll
Microsoft.Practices.EnterpriseLibrary.Configuration.dll
Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.dll
Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Logging.dll
Microsoft.Practices.EnterpriseLibrary.Logging.dll

------------------------------------------------------------------------------------------------------------
so I had them strong named using mycompany.snk key and then complied
each, which went successful. And once I referenced them properly in
the project it compiled without any problems. So far so good.
However when I access the Cache Factory while loading the application
I get hte following error:

An unhandled exception of type 'System.IO.FileNotFoundException'
occurred in microsoft.practices.enterpriselibrary.configuration.dll

Additional information: File or assembly name
Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Logging, or
one of its dependencies, was not found.

------------------------------------------------------------------------------------------------------------

Any ideas how why this is happening and how may I go around it....

Thanks a lot.
Fahd

 

[Shaun C McDonnell]

Fahd,

Microsoft.Practices.EnterpriseLibary.Configuration is not able to find the
Logging dll OR it is not able to find an assembly that the Logging dll
references. Use the ildasm tool on the Logging DLL to see what the problem
is.

 

[fahd]

Thanks for the quick reply Shaun,

Using the ildasm tool and looking in the manifest of logging DLL it
seems that there is a mention of the configuration dll . is there a
path written somewhere in manifest of the location of the dlls
referred too?

thanks

 

[Shaun C McDonnell]

In this case, it would be a good idea to put them into the GAC.

 

[fahd]

I've done that as well. But no luck!

So all of these

Microsoft.Practices.EnterpriseLibrary.Caching.dll
Microsoft.Practices.EnterpriseLibrary.Common.dll
Microsoft.Practices.EnterpriseLibrary.Configuration.dll
Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.dll
Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Logging.dll
Microsoft.Practices.EnterpriseLibrary.Logging.dll

are in the GAC signed with the same public key token.

 

[fahd]

I've done that as well. But no luck!

So all of these

Microsoft.Practices.EnterpriseLibrary.Caching.dll
Microsoft.Practices.EnterpriseLibrary.Common.dll
Microsoft.Practices.EnterpriseLibrary.Configuration.dll
Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.dll
Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Logging.dll
Microsoft.Practices.EnterpriseLibrary.Logging.dll

are in the GAC signed with the same public key token.

 

[fahd]

I've done that as well. But no luck!

So all of these

Microsoft.Practices.EnterpriseLibrary.Caching.dll
Microsoft.Practices.EnterpriseLibrary.Common.dll
Microsoft.Practices.EnterpriseLibrary.Configuration.dll
Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.dll
Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Logging.dll
Microsoft.Practices.EnterpriseLibrary.Logging.dll

are in the GAC signed with the same public key token.

 

[fahd]

I've done that as well. But no luck!

So all of these

Microsoft.Practices.EnterpriseLibrary.Caching.dll
Microsoft.Practices.EnterpriseLibrary.Common.dll
Microsoft.Practices.EnterpriseLibrary.Configuration.dll
Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.dll
Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Logging.dll
Microsoft.Practices.EnterpriseLibrary.Logging.dll

are in the GAC signed with the same public key token.

Ive managed to resolve it now it was an unsigned entry in one of the
config files...