My managed application has a few dependencies on unmanaged DLLs. Even though my unmanaged DLLs are deployed in my bin folder they don’t get loaded. I already found a (hopefully) outdated SO post which points out two possible solutions:
- add dlls to a well-known lookup path (e.g. \System32\Inetsrv)
- add my bin folder to PATH
However, I don’t like either solution as it basically adds a dependency outside my deployment folder (=outside my jurisdiction). Can’t I let IIS know to load an unmanaged DLL (e.g. through web.config)?