Mixed Assembly Problems

[Guest]

I have a managed C++ based assembly referencing a bunch of unmanaged DLLs. I
strongly name the the mixed assembly, and place it in the GAC. I write a VB
client and reference the managed assembly:

1) What does the managed assembly look at to decide where to look for the
unmanaged DLL dependencies?

2) Why do I run into difficulties running clients EXEs (e.g., VB) against
the GAC based assembly?

I'm using VS2005 for all.

 

[Mattias Sjögren]

1) What does the managed assembly look at to decide where to look for the
unmanaged DLL dependencies?

The standard LoadLibrary rules.
http://msdn.microsoft.com/library/en-us/dllproc/base/dynamic-link_library_search_order.asp

2) Why do I run into difficulties running clients EXEs (e.g., VB) against
the GAC based assembly?

I don't know. What kind of difficulties?


Mattias

 

[Guest]

Diffuiculties include messages like the following whenever I run any client
app that references the GAC based assembly:

It's like it cannot find the GAC based assembly or one of its dependencies.
It's dependencies include unmanaged DLLs located back in the GAC based
assembly's build directory.