Hi,
I have an odd problem. IIS loads legacy ISAPI extention and IIS module, both use DLL with same name, however these DLLs are diffrent (linked against different versions of thirdparties). So far there should be no problem, each component (extention and module) reside in their own olders, each one with its own version of DLL, but when IIS starts the worker process and extention and module got loaded somehow the extention tries to load the DLL from the module's folder. I've inspected the module's code and found use of SetDllDirectory which affects the whole process. Voila, this is the problem, I said. after getting rid of this call (replaced with LoadLibraryEx with DLL search flags which suites my needs) the problem persisted. Finaly I found myself with giving unique names to both of these DLLs, which obviously (or not) solves the problem. However it is not clean and elegant solution. Is anyone has any idea why IIS exhibits such a strange behaviour?
Running Win2008, IIS7.5, ISAPI extention - native, C++, VC2010, IIS Module - native, C++, VC2010, above problematic DLL - C++/CLI, linked with .NET3.5 third party assemblies.
Thanks in advance