No, the ISAPI setup would be more complex. You'd still be creating its own directory, but instead of allowing exe you'd be applying the ISAPI Extension as a Global Applicatin Mapping, and then it'd still need added to the Web Service Extension list. CGI's definitely easier.
There's also the fact that the ISAPI Extension is our own custom code which, while we don't know of anything that should cause problems, is still code that must interact with an IIS that we haven't tried. CGI is just running a CGI program.
Have you create the scripts directory and given it execute permissions?
It looks like there are some things beyond the creation that need to be done in IIS7 - This site looks to have some good screen-by-screen instructions, except you'll want Request Path to be "*.exe" instead of "*.cgi", and use the full path to your texis.exe in the scripts directory instead of "zoom\search.cgi".
I changed the ScriptRoot to where my scripts are located. I even left the default. I assume it's not looking at the correct location of the script. Here's what's in the vortex.log:
002 2008-12-04 16:27:02 /scripts/texis.exe/runtest: Cannot open source file: No such file or directory
Would you know why the PATH_INFO includes '/scripts/texis.exe'?
The first part (/scripts) is your virtual directory.
The next (/texis.exe) is the executable in the virtual directory to run.
Everything after that (/runtest) is the script that you want to run.
