Collecting code coverage in an IIS ISAPI DLL

This tutorial describes how to collect code coverage in an IIS ISAPI DLL.

This tutorial covers the following:

    1. Modifying an ISAPI DLL to use the NT Service API.
    2. How to use the Coverage Validator user interface to collect code coverage in the IIS ISAPI DLL.

Related tutorials:

Code coverage for a service.
Collecting code coverage for an application that is a child process of a service.
Code coverage of ASP.Net with IIS.
Collecting code coverage for ASP.Net with Web Development Server.
Collecting code coverage for a child process.

Native ISAPI and mixed-mode ISAPI

This tutorial applies to all native ISAPI DLLs and to mixed-mode ISAPI DLLs that uses the native Win32 services API.


Coverage Validator ships with an example ISAPI DLL in the examples\isapiExample folder in the Coverage Validator installation directory.

The ISAPI DLL has already been modified to use the NT Service API. In this tutorial we’ll describe the modification you would make to the ISAPI DLL to make it work correctly with Coverage Validator.

What is the NT Service API?

The NT Service API is a simple API that allows you to load the Coverage Validator profiling DLL and start the process of collecting code coverage.

The API also includes some debugging functions to help provide debugging information via log files (the only way to get data out of an ISAPI DLL without a connection to the Coverage Validator user interface).

Modifying your ISAPI DLL to use the NT Service API

  1. Identify your service’s GetExtensionVersion() function, and just before that function, add a new function definition called attachToCoverageValidator()

    The purpose of attachToCoverageValidator() is to use the NT Service API to instrument the ISAPI DLL with Coverage Validator.

    // code to load Coverage Validator into the IIS process for this ISAPI
    // this assumes the ISAPI is in C:\testISAPIWebsite\
    #include "..\..\svlCVStubService\svlCVStubService.h"
    #include "..\..\..\svlCommon\svlServiceError.h"
    static void attachToCoverageValidator()
        SVL_SERVICE_ERROR   errCode;
    #ifdef IS6432
        // x86 with x64 GUI
        errCode = svlCVStub_LoadCoverageValidator6432();
    #else   //#ifdef IS6432
        // x86 with x86 GUI
        // x64 with x64 GUI
        errCode = svlCVStub_LoadCoverageValidator();
    #endif   //#ifdef IS6432
        if (errCode != SVL_OK)
            DWORD   lastError;
            lastError = GetLastError();
            svlCVStub_writeToLogFileW(L"Coverage Validator load failed. \r\n");
            svlCVStub_writeToLogFileW(L"Coverage Validator load success. \r\n");
            errCode = svlCVStub_StartCoverageValidatorForIIS();
            if (errCode != SVL_OK)
                DWORD   lastError;
                lastError = GetLastError();
                svlCVStub_writeToLogFileW(L"Starting Coverage Validator failed. \r\n");
            svlCVStub_writeToLogFileW(L"Finished starting Coverage Validator\r\n");
  2. At the start of GetExtensionVersion() just after setting the ISAPI description pVer->lpszExtensionDesc add a call attachToCoverageValidator().
  3. At the end of TerminateExtension() add a call to svlCVStub_UnloadCoverageValidator().

Collecting code coverage in the service

Now that the NT Service API has been implemented in your service, we can start collecting memory allocation data from the service.

  1. Choose the Launch > Services > Monitor IIS and ISAPI… option.

    Coverage Validator launch menu IIS and ISAPI

  2. The Monitor IIS and ISAPI dialog is displayed.

    Coverage Validator IIS and ISAPI dialog

    1. Select the ISAPI DLL you are going to monitor. For this example, the application is C:\testISAPIWebsite\isapiExample_x64.dll. This assumes that IIS has been configured for this ISAPI DLL.
    2. Choose the appropriate native/mixed-mode/.Net option to specify which types of code you want to collect code coverage for. Mixed-mode is the default, as this collects memory allocation information for all types of code.
    3. The web root will be automatically set to the same directory as that containing the ISAPI DLL. Directory permissions for the current user and for user group IIS_ISURS will be automatically set if the Automatically set directory permissions check box is selected. If this is not selected, permissions won’t be set, and a Show me how… link will be displayed beneath the web root. This link will open a tutorial explaining how to set the correct directory permissions to work with IIS_ISURS.
    4. Select a web browser of your choice. For this example we’ll choose firefox.exe.
    5. Specify the URL that you wish to test with the ISAPI DLL. For this example we’re going to test http://localhost:81\isapiExample_x64.dll?10
  3. When you click OK, Coverage Validator will set up everything needed to interact with the IIS and the NT Service API and if all is OK, the web browser will be started to open the specified URL.

    If errors are found you will be presented with a dialog box specific to the error so that you can correct the error before starting the web browser.

  4. Coverage Validator will instrument your ISAPI DLL and start collecting code coverage data.

Finishing collecting code coverage

To finish collecting code coverage, you need to stop IIS.

If you had selected Stop IIS when web browser is closed on the Monitor IIS and ISAPI dialog then you have nothing to do.

Otherwise, choose Launch > Services > Stop IIS

Coverage Validator ISAPI stop IIS

Coverage Validator will collect code coverage through the service shutdown procedure and then present you with the complete code coverage data.

I’m not getting any code coverage data. What can I do?

There are a few things to check.

  1. Have you correctly added the NT Service API to the ISAPI DLL? 
  2. Check the log file for any errors. You specified the log file in attachToCoverageValidator() with the call
  3. Check the diagnostics tab. If the NT Service API is working correctly, Coverage Validator will have some data. Information on instrumentation failures will be on the diagnostic tab.
  4. Check the debug information dialog. You can access this from the Tools > DLL Debug Information… menu. This dialog will tell you which DLLs have debug information and which do not. Any DLLs that don’t have debug information you’ll need to ensure that debug information is built for these DLLs and is findable.


You have learned how to add the NT Service API to an ISAPI DLL, how to use Coverage Validator to monitor ISS and ISAPI, and what to look at to diagnose errors if things don’t work first time.



Fully functional, free for 30 days