G
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.
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.