Create instance which depends on external dll

[slaks]

During runtime i need to load some dll.
Assembly.LoadFile works ok, but when i invoke CreateInstance on some type
from this dll it throws me exception because my type depends on dll's which are in the same directory.

My question is : how can i create instance when it depends on external dlls which the systems can not locate.

Thanks

Slava.

[krodman]

Ensure that the dependent DLL's are in the same directory as the DLL you're trying to load.

[slaks]

Ensure that the dependent DLL's are in the same directory as the DLL you're trying to load.

The dependent dlls are in the same directory

[krodman]

Sorry about that, I guess I wasn't reading carefully enough.

Have you recompiled any or all of the dependent DLL's since having compiled the DLL you are trying to load? I'm not 100% sure, but I think this a versioning issue.

I've ran into a similar situation where I was trying to load a DLL that had been compiled with an older version of the referenced assemblies than what was is the current directory. Recompiling the DLL seemed to do the trick. However, later I created interfaces for my referenced assemblies, and referenced those instead. This way I can make changes to the referenced assemblies, without having to recompile the DLL I'm attempting to load.

[slaks]

Yes, all the dlls are part of one project so they are recompiled in synch.
I guess the problem in the way CLR looks for assemblies.
I tried to put my dlls in some subdirectory of the executable directory and give the CLR probing path. Everything worked fine.
But probing works only with subdirectories relative to the executable.
And the question is - is it possible to do the same with any directory (probably not)