Re: Missing libraries

Fuslogvw.exe is part of the Windows SDK.  On my machine, it's at C:\Program
Files\Microsoft SDKs\Windows\v6.0A\bin.  I don't know if it's self-contained
such that it can just be copied to another machine.
And Shawn is right -- EXE < DLL dependencies aren't the problem; it's
dynamic loading of DLLs that are in a different directory where Fusion
starts to bite you.

On Thu, Jan 22, 2009 at 10:15 AM, Eddie Lascu <[email protected]> wrote:

> Hi Curt,
>
> I don't know the tool you are referring to. Will have to investigate it. Is
> it freely downloadable somewhere?
>
> Anyway, I found some reference on the Internet and they told me to check
> the
> Event Viewer for SideBySide errors. I did find three entries that are
> generated by my app every time the exception is raised. Here is the content
> of those entries:
>
> Generate Activation Context failed for D:\CHP\exe\ATMSDataClient.dll.
> Reference error message: The referenced assembly is not installed on your
> system.
>
> Resolve Partial Assembly failed for Microsoft.VC80.DebugCRT. Reference
> error
> message: The referenced assembly is not installed on your system.
>
> Dependent Assembly Microsoft.VC80.DebugCRT could not be found and Last
> Error
> was The referenced assembly is not installed on your system.
>
> So it's clear to me now that the Microsoft.VC80.DebugCRT is missing. What
> is
> not clear is why is my application even looking for that since both the
> application and the library are generated in their Release configuration.
> Ultimately, I can add this missing assembly, but I will try first to figure
> out how to get away by not using it.
>
> Regards,
> Eddie
>
>
>
> -----Original Message-----
> From: Discussion of advanced .NET topics.
> [mailto:[email protected]] On Behalf Of Curt
> Hagenlocher
> Sent: Thursday, January 22, 2009 12:52 PM
> To: [email protected]
> Subject: Re: [ADVANCED-DOTNET] Missing libraries
>
> Have you tried running the Fusion log viewer (fuslogvw) to chase this down?
> The CLR loader (aka Fusion) won't automatically load dependent assemblies
> just because they're in the same directory.  Is it possible that -- in your
> development environment -- the dependent assemblies are either in your path
> or in the GAC?
>
> On Thu, Jan 22, 2009 at 9:49 AM, Eddie Lascu <[email protected]> wrote:
>
> > Hello experts,
> >
> > 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?
> >
> > Any suggestion will be highly appreciated.
> > Regards,
> > Eddie
> >
> > PS: here is the full message of the exception
> >
> > Could not load file or assembly 'ATMSDataClient,
> > Version=1.0.3250.18364, Culture=neutral, PublicKeyToken=null' or one
> > of its dependencies. This application has failed to start because the
> > application configuration is incorrect. Reinstalling the application
> > may fix this problem. (Exception from HRESULT: 0x800736B1)
> >
> >
> > ===================================
> > 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
>
> ===================================
> 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