Setting the path of an ISAPI dll file creation

Question

I am working on a project where I use an ISAPI dll file/web service to generate a file. I previously used a hardcoded location as to where to store the file, which worked great, I am now trying to swap it with a location stored within a specified text file.

The problem I am having is that it seems to be appending the current path of the IIS worker process 'C:\Windows\SysWOW64\inetsrv' to the start of the location information I store inside my text file. I am not sure if this is down to my code or an IIS 7 server setting? Can anyone point me in the right direction?

Many Thanks.

Where do you expect the file to be stored? What's the path you use to store it? — jachguate, Jan 16 '13 at 17:17
The file location can change, at the moment I am trying to put it in a test folder on my e drive, i.e. 'e:\testfolder\', but the location is being prefixed with the C:\Windows\SysWOW64\inetsrv. — user1085959, Jan 16 '13 at 17:33
@user don't like like nonsense, but your question still lacks some code to figure out what's going on. — jachguate, Jan 16 '13 at 21:20

Hugues Van Landeghem · Answer 1 · 2013-01-16T18:28:28.627

I think you have to use SetDllDirectory in MSDN

After calling SetDllDirectory, the standard DLL search path is:

The directory from which the application loaded.
The directory specified by the lpPathName parameter.
The system directory. Use the GetSystemDirectory function to get the path of this directory.The name of this directory is System32.
The 16-bit system directory. There is no function that obtains the path of this directory, but it is searched. The name of this directory is System.
The Windows directory. Use the GetWindowsDirectory function to get the path of this directory.
The directories that are listed in the PATH environment variable.

score 0 · Answer 2 · answered Jan 16 '13 at 20:14

This is not a direct answer, but may put you in the right direction. Working on the http://xxm.sf.net/ project, I've found you can set the current directory (for the process) from within the ISAPI dll. It appears that inetinfo.exe/dllhost.exe/w3wp.exe (or any other process IIS uses to call your ISAPI from) doesn't mind and keeps operating normally.

Setting the path of an ISAPI dll file creation

2 Answers2