Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

enabling ISAPI on Vista

0 views
Skip to first unread message

Jeremy

unread,
Mar 7, 2008, 3:01:35 PM3/7/08
to
I thought I had this part nailed, but it ain't workin right.

On my local system I've added a scripts folder to c:\inetpub\wwwroot. I
converted it to an application. In Handler Mappings, I've enabled
isapi-dll.

Now, I copy a dll to scripts, restart the website. The url
http://localhost/scripts/mydll.dll gives me the file download/open with
what? message. Why doesn't it run?

Just to confound things: yesterday I was able to create an isapi dll,
compile it in D7 and run it from a url. (I added the application as a
reference to the actual project folder).

It's like IIS is saying "sorry, you've had enough fun. Now I'm going to
stop playing with you"

Any hints?

Del Murray

unread,
Mar 7, 2008, 8:28:45 PM3/7/08
to
See what this does ..


In the Turn Windows Features on or off select the World Wide Web Services
and manually also turn on CGI, ISAPI Extensions and ISAPI Filters. Start the
IIS Manager and select the ROOT (server) and ensure you're in feature view.
Select the Handler Mappings. You should see CGI and ISAPI there as disabled.
Select ISAPI and select Edit Handler Permissions. Check the Execute option
and press OK. ISAPI and CGI should now appear as enabled.

Dont know anything about VISTA except that it might be a brand of toilet
paper. Found this on the web.


Jeremy

unread,
Mar 8, 2008, 2:17:50 PM3/8/08
to
Del, I appreciate the help. I do have all these settings just as you
describe them, and my question was "why does it still not work?"

Rick Francken

unread,
Mar 9, 2008, 9:39:12 AM3/9/08
to
Have you explicitly added your ISAPI DLL to the Web Server Extensions? In IIS 6
onward, nothing is turned on by default. So you have to add your ISAPI Dlls
explicitly to the server extensions.

I'm still trying to learn the new IIS 7 interface, as it has changed again from
IIS 6, and at first glance is not very intuitive. In IIS 6, you had to add your
ISAPI Dll in the Web Server Extensions folder, which IIRC, was one of the main
subfolders under IIS. Hope this points you in the right direction.

Rick Francken

Jeremy

unread,
Mar 9, 2008, 1:03:55 PM3/9/08
to
"Rick Francken" <ri...@franckensoft.com> wrote in message
news:47d3e87c$1...@newsgroups.borland.com...

> Have you explicitly added your ISAPI DLL to the Web Server Extensions? In
> IIS 6 onward, nothing is turned on by default. So you have to add your
> ISAPI Dlls explicitly to the server extensions.

Rick, I'm not finding any way to explicitly add a dll to Web Server
Extensions. I can add a new application, which amounts to creating a
virtual folder pointing to my app folder where the dll lives. If I enable
isapi-dll in Handler Mappings, I can run a simple test dll (displays a
couple of test boxes & has a button to click). However, I created a scripts
folder, "converted" it to an application, and the dll does not run.

0 new messages