In IIS7, we have an application which comes supplied as a .dll file. Application is known to work in II6 on a different server.
When browsing the URL of this application, it sends the .dll itself as a binary file (giving prompt of "Download: do you want to open or save this file" in the browser). For the application to work, we want ISAPI to run the DLL and send the resulting HTML.
What could be the problem? What needs to be configured to make this work? We've tried adding the specific .dll file to both IsApiFilters or to a Script Map in HandlerMappings (using handler IsApiModule). Module list shows that IsApiModule is Loaded.
The server-wide list of Handler mappings shows ISAPI-dll in the Disabled section with Path:"*.dll", Path type: "file". Is this entry relevant? Can it somehow be moved into the Enabled section?
[using IIS Manager GUI to edit settings]