Shravan Vasista

> @wmmc88 it looks like one of the docs jobs hanged. Can you restart it or bypass it? Ah. Hanged on winget installation. Winget installation is primarily used to get...

This sample driver makes an illegal call to `KeEnterCriticalRegion` in its `evt_device_d0_exit` which violates the `IrqlKeApcLte2` rule. When Driver Verifier is enabled for this fail driver, the fault can be...

`cargo-wdk` is a Command-Line Interface (CLI) utility that can be used to create and build Windows driver projects that depend on the WDK and `windows-drivers-rs` platform. It aims to streamline...

feat: enable CI workflows to use NuGet WDK packages

2

Enables the CI pipeline to use NuGet WDK/SDK packages instead of WinGet WDK installation. These changes allow the workflows to use multiple WDK versions in the matrix. NOTE: The latest...

Updated the driver class for fail_driver_pool_leak to Sample. Added missing steps to the Fail_Driver_Pool_Leak Sample Driver README to improve clarity and usability.

This PR includes changes to the `build` command to respect other forms of target configuration vis config.toml (`build.target`) and environment (`CARGO_BUILD_TARGET`) along with the `--target` CLI option. ### Logical Changes...

Validate parameters supplied to the cargo-wdk build command

3

The build subcommand currently constructs and runs BuildAction with minimal upfront checks. Many user errors aren’t surfaced until after WDK detection, PATH setup, or partial per‑package iteration. Early validation will...

Use the latest versions of headers available in the Kit by default (short term), and be metadata configurable (medium term)

5

Not to be addressed in this pr, but we should track making all of these use the latest in the short term, and be metadata configurable in the medium term...

Support for extended paths (cargo-wdk)

2

Windows “extended” / “verbatim” paths (prefix \?\ for local/UNC, or \?\UNC\ for network) bypass legacy MAX_PATH (260) parsing and disable some normalization (e.g. no trimming of trailing dots/spaces, no interpretation...

`cargo wdk build` does not match `cargo build` behavior for workspaces

2

Noticed a bug in `cargo-wdk` when trying to build the [samples](https://github.com/microsoft/Windows-rust-driver-samples) workspace. Steps to repro: 1. `cd` into Windows-rust-driver-samples\general\echo 2. Run `cargo build`. It successfully builds the entire workspace 3....