Information
The topic you requested is included in another documentation set. For convenience, it's displayed below. Choose Switch to see the topic in its original location.

New for Driver Development Tools

The Windows Driver Kit (WDK) that is released with Windows 8 includes the following changes to driver development tools and technologies.

DDI Compliance Rules

The DDI Compliance Rules define requirements for the proper interaction between a driver and the kernel interface of the operating system. The DDI Compliance Rules have been updated with links to testing information and links to the relevant DDIs for WDM, KMDF, NDIS, and Storport. The DDI reference pages include links to the related rule pages. The rule pages are organized by rule sets, for example, IRQL rules, IRP tracking.

Static Driver Verifier

Now supports Storport drivers, in addition to KMDF, WDM, and NDIS drivers. Requires driver-supplied functions to be declared by Using Function Role Type Declarations.

Static Driver Verifier is now integrated and launched from Visual Studio. For more information, see Static Driver Verifier.

Driver Verifier

Driver Verifier has new options, DDI compliance checking, Power Framework Delay Fuzzing, Invariant MDL Checking for Stack, Invariant MDL Checking for Driver, and Stack Based Failure Injection.

The Power Framework Delay Fuzzing option randomizes thread schedules to help detect concurrency bugs in the driver.

The DDI compliance checking option applies the same device driver interface (DDI) usage rules that Static Driver Verifier uses to verify that your driver makes function calls at the required IRQL for the function. DDI compliance checking is run as part of the standard Driver Verifier options. When you build, deploy, and test your driver using Visual Studio, you can also configure Driver Verifier to run on a test computer when you deploy your driver for testing.

For more information, see Driver Verifier.

Code Analysis for Drivers

In previous versions of the WDK, the driver-specific module for code analysis was part of a stand-alone tool called PREfast for Drivers (PFD). PREfast for Drivers was also integrated into the WDK Build environment, as part of Microsoft Automated Code Review (OACR). Starting with Windows Driver Kit (WDK) 8, the driver-specific features have been integrated with the Code Analysis tool in Visual Studio. For more information, see Code Analysis for Drivers.

Tools for building drivers

The WDK for Windows 8 contains a major change to the build environment that you use to build a driver. The WDK build environment no longer uses Build.exe. The WDK build environment for drivers uses MSBuild.exe and is fully integrated with the Visual Studio development environment.

For more information, see Building a Driver and the WDK and Visual Studio build environment.

Tools for testing Drivers

The WDK 8 is integrated with Visual Studio (Microsoft Visual Studio Professional 2012 or Microsoft Visual Studio Ultimate 2012). Using the WDK you can build, deploy, and test your driver on a remote test computer without leaving Visual Studio. The WDK also provides the Device Fundamental tests, a core set of tests that are used as part of the Windows Hardware Certification Program. You can customize these tests or write your own, using the provided Driver Test templates. For more information, see Testing a Driver.

 

 

Send comments about this topic to Microsoft

Show: