This repo contains driver samples prepared for use with Microsoft Visual Studio and the Windows Driver Kit (WDK). It contains both Universal Windows Driver and desktop-only driver samples.
First of all, changing logging for an existing feature: When you pass in the -Samples flag we will filter to only run samples matching provided filter argument. Say, if you call with -Samples '^tools.' we will only run on samples in the tools folder. This functionality remains unchanged. The verbose log however now refers to these samples as "filtered in" vs "filtered out". Prior to this PR the term "excluded" was used, but this term is also used elsewhere.
Secondly, this PR extends PowerShell script so exclusions can be tied to a specific WDK build number. This "fixes" an annoying problem that our publicly available WDK (currently 22621) works on slightly different samples than our internal WDK (not yet released publicly).
Finally, and most importantly, this PR provides an updated, detailed and accurate fine grained exclusion.csv file. This file takes advantage of the build number feature discussed above. This file also takes advantage of a feature introduced earlier to exclude based on [platform|configuration]. This updated exclusion.csv file is accurate for "in market" 22621 WDK (also used by GitHub) and our internal WDK (not yet released publicly). To see this file I recommend you use the nice rendering mechanicsm github provides for CSV files. See here: https://github.com/microsoft/Windows-driver-samples/blob/develop/exclusions.csv
This PR does following:
First of all, changing logging for an existing feature: When you pass in the -Samples flag we will filter to only run samples matching provided filter argument. Say, if you call with -Samples '^tools.' we will only run on samples in the tools folder. This functionality remains unchanged. The verbose log however now refers to these samples as "filtered in" vs "filtered out". Prior to this PR the term "excluded" was used, but this term is also used elsewhere.
Secondly, this PR extends PowerShell script so exclusions can be tied to a specific WDK build number. This "fixes" an annoying problem that our publicly available WDK (currently 22621) works on slightly different samples than our internal WDK (not yet released publicly).
Finally, and most importantly, this PR provides an updated, detailed and accurate fine grained exclusion.csv file. This file takes advantage of the build number feature discussed above. This file also takes advantage of a feature introduced earlier to exclude based on [platform|configuration]. This updated exclusion.csv file is accurate for "in market" 22621 WDK (also used by GitHub) and our internal WDK (not yet released publicly). To see this file I recommend you use the nice rendering mechanicsm github provides for CSV files. See here: https://github.com/microsoft/Windows-driver-samples/blob/develop/exclusions.csv
How tested:
In Environment: GitHub 22621:
(Example for x64 Debug) Samples: 138 Configurations: 1 (Debug) Platforms: 1 (x64) Combinations: 138 Succeeded: 131 Excluded: 7 Unsupported: 0 Failed: 0
In Environment: WDK 22621:
Samples: 138 Configurations: 2 (Debug Release) Platforms: 2 (x64 arm64) Combinations: 552 Succeeded: 286 Excluded: 30 Unsupported: 236 Failed: 0
In Environment: EWDK 22621:
Samples: 138 Configurations: 2 (Debug Release) Platforms: 2 (x64 arm64) Combinations: 552 Succeeded: 286 Excluded: 30 Unsupported: 236 Failed: 0
In Environment: EWDK 26031:
Samples: 138 Configurations: 2 (Debug Release) Platforms: 2 (x64 arm64) Combinations: 552 Succeeded: 290 Excluded: 26 Unsupported: 236 Failed: 0