Problems in loading unmanaged(non COM) dll.

  • Thread starter Thread starter Mandeep Singh
  • Start date Start date
M

Mandeep Singh

Development Scenario:
+++++++++++++++++++++
1) I am developing a Visual c# web application.
2) It uses a mixed-mode Managed dll(containing Managed c++
code).
3) This managed dll in turn has static dependency on an
unmanaged(non COM) dll. Note that this dll does not contain
a valid COM component.

What i did:
+++++++++++
1) In my Visual .NET studio for my c# web application, i
created a reference for the managed dll. Also, i put the
unmanaged(non COM dll) in the system Path. As a result of
all this, my c# web application ran perfectly fine.
2) Now i removed the unmanaged(non COM) dll from the system
path. I placed this unmanaged(non COM) dll in my c# web
application's bin directory(not in the system path). Now
when i try running my web application, it gave me an error
message saying "Some error occured while loading the
managed dll or one of its dependencies".

The Real Problem:
+++++++++++++++++
My second test case(mentioned above) doesnt work. Does this
mean that putting the unmanaged(non COM) dll in the system
path is the only way out?
 
Hi,

Any unmanaged DLL is searched by the rules outlined in the LoadLibrary API
documentation. Please search the MSDN Library for the "LoadLibrary" and
"SetDllDirectory" topics.
 
Back
Top