WDF on GitHub FAQ

How do I build the WDF source?

We currently don’t support building WDF source code.

How do I contribute to the WDF source?

See CONTRIBUTING.md for details.

I think I've found a bug what should I do?

File an issue on this repo. Please include a clear description of the issue and, if possible, details of where in source the problem occurs. Any relevant info about you're test environment and instructions on how to repro the bug would also be appreciated.

There's a feature I think would be really helpful, What should I do?

As with bugs, file an issue on this repo. We'll collect all the feature requests and review them when we do our iteration planning.

I've noticed some blocks of empty lines in the source, what's with that?

We've stripped some comments from the source that refer to Microsoft internal work tracking, engineering staff, etc. We could have cut those empty lines but it's important for debugging with source that line numbers match up exactly with the symbols we publish.

How much of the WDF source has been published?

With this initial release, we've published the source that's useful for debugging KMDF and UMDF v2 drivers. Source for UMDF v1 or for infrastructure components like the UMDF redirector are not included. Plans for increasing the scope of the published source are under consideration.

What’s the WDF DDI count check?

The DDI count check ensures that WDF drivers have been compiled against the correct version of WDF. If the number of DDIs the driver expects to find doesn’t match the number of DDIs that WDF actually exposes, then the driver will crash. Early in the Windows development cycle, as the DDI set is changing frequently, the WDF team disables this check. It’s re-enabled before public Windows releases.

Where can I learn more about WDF?

Most of the WDF documentation lives on MSDN. You can also read from Developing Drivers with the Windows Driver Foundation, which is still very relevant.