Re: OT [was: Missing libraries]

Thank you Fabian,

I will definitely check Fusion log viewer, since it was recommended by
several others. In the mean time I solved my problem using Dependency
Walker. This tool not only tells you what libraries are required by the
application, but actually searches for them and gives you a list of things
that are missing. Very useful!

Thanks again,
Eddie



-----Original Message-----
From: Discussion of advanced .NET topics.
[mailto:[email protected]] On Behalf Of Fabian Schmied
Sent: Friday, January 23, 2009 6:21 AM
To: [email protected]
Subject: Re: [ADVANCED-DOTNET] OT [was: Missing libraries]

> I have this project that works fine on my development environment. It 
> uses several .dll libraries. The problem is that once I deploy it on 
> the production environment I get some exceptions informing me that the 
> application could not load one of my .dlls. Now I clearly see the .dll 
> in the same folder, so this is not a problem of not having the 
> library. I am guessing must be one of its dependencies that are 
> missing on the production server.
>
> Is there a way I can find all the libraries on which my dll is further 
> dependent?

There are several ways, for example:
- You can use ILdasm.exe, which comes with the .NET SDK. (Open the assembly,
click on "MANIFEST", look at the assembly extern
directives.)
- You can use Red Gate's .NET Reflector.

However, the easiest way to debug such an exception is the Fusion log
viewer. I've blogged about it here:
<https://re-motion.org/blogs/mix/archive/2009/01/23/could-not-load-something
-or-something-else.aspx>.

Regards,
Fabian

===================================
View archives and manage your subscription(s) at
http://peach.ease.lsoft.com/archives

===================================
View archives and manage your subscription(s) at http://peach.ease.lsoft.com/archives