We assume that you are familiar with IIS. This is not a topic we can provide advice for.
That said, we wrote a blog article about configuring IIS for use with ISAPI.
We have provided an example ISAPI extension configured for use with Bug Validator.
This example is provided as source code and project files. You will need to build it yourself, you may need to change an include path to find the appropriate headers. The resulting ISAPI will need to be copied to your website for testing and the website configured to allow the ISAPI to execute (please see the above mentioned blog article for details on that).
You can find the example ISAPI in the isapiExample folder in the Bug Validator installation directory.
IIS is a service application. It runs as one of the more restricted applications on Microsoft Windows.
Bug mapped files created by IIS cannot be opened by user mode programs (Bug Validator, for example). DLLs, executables and files cannot be opened by IIS except if they are in directories which IIS has access to. These are security measures intended to make your computer secure from attack.
These security measures make it hard for tools like Bug Validator to work.
•We have to communicate settings information to Bug Validator via text file
•All DLLs and helper programs we want to use need to be copied to the web root (or a subdirectory within the web root) so that they can be used.
•We need to have our own data transport because our usual high speed memory mapped data transport is not available.
It's also not possible to launch IIS or inject into a running IIS instance.
The only way to work with IIS is by using the NT Service API, and using the svlBVStub_StartBugValidatorForIIS() function instead of svlBVStub_StartBugValidator().
We've provide some example code to show you how to attach and detach from your ISAPI extension.
Launch menu IIS menu Monitor ISAPI...
2) When you have finished interacting with the web pages that use the ISAPI component shutdown IIS, wait for Bug Validator's status to indicate "Ready" and examine the results.
Launch menu IIS menu Stop IIS