Re: Enabling dlls in IIS 7.5

Understood. I was hitting F5 and Ctrl-F5 and Ctrl-Shift-F5, and even clearing my browser history, but it was still happening. And this was at the point where I knew the configuration had been corrected, and saw that it was working in other browsers, so I suspected a caching issue.

I believe the problem has to do with the fact that when hitting the link, Chrome was opening another tab and giving the 'save or open wc.dll' prompt at the bottom of that page. When I would select 'Discard', that new tab would automatically close and I would be back on the original, unchanged tab/page. That is, I wasn't really able to hit F5 on the proper page/link - it was discarded, and I could really only refresh the page that was already working (which was using a proper scriptmapped link).

I had to use 'Developer Tools / Settings / Disable Cache' and then my next attempt worked, along with all further attempts with the cache re-enabled.

- Mike McDonald
Software Design of Kentucky

You should ALWAYS hit F5 (or Ctrl-R) to refresh pages that need anything fixed. Otherwise browser caching kicks in - GET requests are cached by default so they typically will not refresh and less you do a hard refresh.

+++ Rick ---

It wants to save or open the wc.dll.

Glad you got this figured out. I want to mention that if you ever get this 'save or open wc.dll' prompt, and then you make changes that you think should fix the issue, you can still get that prompt even after the IIS configuration has been corrected.

At least in the Chrome browser, I continued to get the 'save or open wc.dll' prompt (after fixing the settings), but when I tried with another browser, it worked fine. Hitting Ctrl-R or Ctrl-Shift-R didn't resolve it. I had to disable the cache temporarily, and then it worked from that point forward.

- Mike McDonald
Software Design of Kentucky

This question is how to enable the wc.dll to run in an IIS 7.5 environment. The documentation is very good, but in only goes up to 7.0.

I have installed the ISAPI and CGI Restriction feature. In there I have set the path to c:\app\site\bin\wc.dll. I have checked the "Allow extension path to execute." In the Handler Mappings I have ISAP-dll enabled, path set to *.dll, Path Type as File, and Handler set to ISAPIModule.

I'm not sure this is right. Well, I'm sure it's not right because it fails. When I type in the url - http://192.168.1.7/mud/bin/wc.dll?FoxInCloud~Default: It wants to save or open the wc.dll.

Any help is appreciated.

TIA.

BR