feat: enable CI workflows to use NuGet WDK packages #236

svasista-ms · 2024-10-14T05:05:48Z

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 WDK version is installed as a NuGet package. Older versions of WDK (before v10.0.26100) still rely on WinGet. On a local computer eWDK environement can be used.

Closes #214 partially. NI WDK and LLVM still use WinGet at the moment.

Summary of changes,

Added the script nuget-install-wdk.ps1 to

Download the specified version of NuGet WDK/SDK packages
Move WDK tools, signtool, certmgr, MakeCert to WDK bin directory to ensure all required binaries are under WDK Tool Root dir
Move ARM64 KM, UM, KMDF, UMDF headers to x64 directory (to mirror standard WDK and EWDK installations)
Set WDKContentRoot ENV variable to NuGet package root for the detect_wdk_content_root function to setup WDK content root path.

Modified workflows to use the above script to install WDK build numbers >= 26100.
Added packages.config that contains WDK packages and dependencies to be downloaded.

…root

…s-drivers-rs into port-pipeline

…getWDKContentRoot env variable

… tools/ for WDK tool root

…ix test

wmmc88 · 2024-10-14T15:53:44Z

crates/wdk-build/src/utils.rs

@@ -98,6 +98,19 @@ pub fn detect_wdk_content_root() -> Option<PathBuf> {
        );
    }

+    // If NugetWdkContentRoot is present in environment, use it
+    if let Ok(wdk_content_root) = env::var("NugetWdkContentRoot") {


I don't think we should be doing custom handling here for nuget since NugetWdkContentRoot doesn't exist normally for the Kit. How does building with nuget generally work in a non-rust environment?

I understand. The C samples use the Build-SampleSet.ps1 script. Adding the NugetWdkContentRoot was one of the ways to point to the NuGet pkg root. I'm not fully aware of how msbuild works with NuGet pkgs and how SxS WDK installations work.

I very much do not want to add new scaffolding to windows-drivers-rs when existing mechanisms exist. In order to make sure this doesn't diverge from the original kit, I think you need to find out how C/C++ WDK handles pointing to the WDKContentRoot when using the new nuget install methods. For eWDK, we check for the env vars that eWDK prompts set. For installed WDK, we look for the reg keys that the WDK installer sets. For nuget, we should use whatever mechanism DDX has for nuget for root discovery. @NateD-MSFT do you have insight/contacts for this?

I'll spin up a thread with the WDK team to ask.

crates/wdk-build/src/cargo_make.rs

wmmc88 · 2024-10-14T15:55:23Z

.github/workflows/build.yaml

@@ -20,6 +20,7 @@ jobs:
      matrix:
        wdk:
          - Microsoft.WindowsWDK.10.0.22621 # NI WDK
+          - Microsoft.Windows.WDK # Latest WDK


Even with nuget, we want to be able to test specific versions of the kit

…d_length_path_prefix

…into port-pipeline

…1 script to install WDK version based on the matrix input, fix clippy issue

…s-drivers-rs into port-pipeline

…shell shell

…_or issue in utils.rs

NateD-MSFT · 2024-11-27T22:52:42Z

tests/mixed-package-kmdf-workspace/crates/driver/src/lib.rs

-    WDF_DRIVER_CONFIG,
-    WDF_NO_HANDLE,
-    WDF_NO_OBJECT_ATTRIBUTES,
+    call_unsafe_wdf_function_binding, ntddk::DbgPrint, DRIVER_OBJECT, NTSTATUS, PCUNICODE_STRING, PDRIVER_OBJECT, ULONG, UNICODE_STRING, WCHAR, WDFDEVICE, WDFDEVICE_INIT, WDFDRIVER, WDF_DRIVER_CONFIG, WDF_NO_HANDLE, WDF_NO_OBJECT_ATTRIBUTES


Not a blocker, but I am curious how this reformat wasn't caught sooner by CI/other pipeline checkins.

I think this change actually needs to be reverted? I suspect that whats going on is that:

cargo fmt check is only run at repo root. AFAIU, it traverses files it sees based on cargo-metadata (ie. it only looks in the workspace)

the mixed-package-kmdf-workspace is actually its own cargo workspace, so that cargo fmt has no idea it exists

There are some gaps in the top-level examples and tests folders where certain pipelines are not fully covering them. spent some time figuring out what gaps there are (mostly due to changes related to #186 ) and will be adding the rundown to github in a pr

wmmc88 · 2024-12-03T17:57:40Z

packages.config

+  <package id="Microsoft.Windows.SDK.CPP.arm64" version="10.0.26100.1591" targetFramework="native" />
+  <package id="Microsoft.Windows.WDK.x64" version="10.0.26100.1591" targetFramework="native" />
+  <package id="Microsoft.Windows.WDK.arm64" version="10.0.26100.1591" targetFramework="native" />
+</packages>


nit: newline at end of file is missing

wmmc88 · 2024-12-03T23:59:16Z

.github/workflows/build.yaml

+          # - 10.0.26100.1882
+          # - 10.0.26100.1591


These are just QFE versions right? I think either have all of the QFE versions enabled, or remove the comment

Also why not use the latest QFE here, if there is only going to be one

I think the best thing to do here is actually leave off the QFE version and get the latest QFE for a given build number

FWIW the varying QFEs here do refer to meaningfully different builds of the WDK now that we've moved to a CD model. It is probably fine to just use the latest GE CD kit for the matrix rather than run each one.

So for a given build number, a user should always be using the latest QFE, right?

FWIW the varying QFEs here do refer to meaningfully different builds of the WDK now that we've moved to a CD model. It is probably fine to just use the latest GE CD kit for the matrix rather than run each one.

Is this WRT to GE only, or do you think its always fine to just run on the latest QFE for every build number(including vNext wdk)? my intuition here is to have the matrix always run:

the latest QFE for every build number

both winget and nuget since they use meaningfully different ways of exposing where its contents are (ie. regkey for winget and vcxproj for nuget, but per my other comment, i think we should piggyback off the ewdks' env var)

I believe that prior to Ge there was no meaningful difference between QFEs. Kits almost exclusively shipped once per release. I think there was a special case in one release, but the concept of "multiple kits with the same build number but different QFEs, with different content" is new to Ge and CD.

wmmc88 · 2024-12-04T00:07:29Z

.github/workflows/build.yaml

@@ -20,6 +20,10 @@ jobs:
      matrix:
        wdk:


Rather than special casing the NI WDK, I think you should explicityly add another matrix dimension for WDK source. Then you can exclude the WDK versions from nuget that aren't available via the exclude feature. It would look something like:

matrix: wdk_source: [nuget, winget] wdk_version: - 10.0.22621 # NI WDK - 10.0.26100 #GE WDK exclude: # 10.0.22621 not available on nuget - wdk_source: nuget wdk_version: 10.0.22621

This way, your later steps can switch on if: matrix.wdk_source == nuget and similar. The Nuget and Winget specific steps should be able to eaisly reconstruct the full install version string from just the wdk_version

wmmc88 · 2024-12-04T00:13:19Z

.github/workflows/build.yaml

+        run: |
+          $wdk = '${{ matrix.wdk }}'
+          if ($wdk -match '^10\.0\.\d{5}\.\d{1,4}$') {
+            ./.github/scripts/nuget-install-wdk.ps1 -wdkVersion $wdk


Needing to run this ps script seems a little hacky. Is there a reason you can't just nuget install the required packages in this run block?

wmmc88 · 2024-12-04T00:15:25Z

.github/scripts/nuget-install-wdk.ps1

+$packagesConfigPath = ".\packages.config"
+
+if (Test-Path $packagesConfigPath) {
+    [xml]$packagesConfig = Get-Content $packagesConfigPath


rather than updating a version thats hardcoded into a packages.config (that is only used in CI), can you just use nuget install in the action step?

wmmc88 · 2024-12-04T21:22:16Z

.github/scripts/nuget-install-wdk.ps1

+    exit 1
+}
+
+$folders = @(


why is there all this manual copying of folders after the nuget packages are restored? this seems very brittle

The setup_path function sets the bin and tools root W.R.T standard WDK's directory structure. However, with NuGet I noticed that some bins and headers were placed in a different path. So, this script moves them under the root that setup_path is using.

windows-drivers-rs/crates/wdk-build/src/cargo_make.rs

Line 515 in 10a8e37

pub fn setup_path() -> Result<impl IntoIterator<Item = String>, ConfigError> {

this function actually uses detect_wdk_content_root, so as long as that's detecting nuget properly, then we're all set.

see #236 (comment) for more details, but the tl;dr is that the nuget WDK's use in c drivers works by setting the include and bin paths via modifying the vcxproj. as stated in my linked comment, since there is no path forward to use the same solution that nuget uses in c drivers (ie. vcxproj is not supported by our rust tooling), we should rely on the env vars used by ewdk

wmmc88 · 2024-12-04T21:32:15Z

@svasista-ms I did some of my own investigation on how C drivers use the WDK via nuget. It looks like when the nuget dependency is added via visual studio ui, the WDK's props and targets are added to the projects vcxproj.

diff --git a/KMDF Driver1/KMDF Driver1.vcxproj b/KMDF Driver1/KMDF Driver1.vcxproj
index 6a4e8cf..8694853 100644
--- a/KMDF Driver1/KMDF Driver1.vcxproj
+++ b/KMDF Driver1/KMDF Driver1.vcxproj
@@ -1,5 +1,8 @@
 <?xml version="1.0" encoding="utf-8"?>
 <Project DefaultTargets="Build" ToolsVersion="12.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
+  <Import Project="..\packages\Microsoft.Windows.WDK.ARM64.10.0.26100.2454\build\native\Microsoft.Windows.WDK.arm64.props" Condition="Exists('..\packages\Microsoft.Windows.WDK.ARM64.10.0.26100.2454\build\native\Microsoft.Windows.WDK.arm64.props')" />
+  <Import Project="..\packages\Microsoft.Windows.SDK.CPP.arm64.10.0.26100.2454\build\native\Microsoft.Windows.SDK.cpp.arm64.props" Condition="Exists('..\packages\Microsoft.Windows.SDK.CPP.arm64.10.0.26100.2454\build\native\Microsoft.Windows.SDK.cpp.arm64.props')" />
+  <Import Project="..\packages\Microsoft.Windows.SDK.CPP.10.0.26100.2454\build\native\Microsoft.Windows.SDK.cpp.props" Condition="Exists('..\packages\Microsoft.Windows.SDK.CPP.10.0.26100.2454\build\native\Microsoft.Windows.SDK.cpp.props')" />
   <ItemGroup Label="ProjectConfigurations">
     <ProjectConfiguration Include="Debug|x64">
       <Configuration>Debug</Configuration>
(1/3) Stash this hunk [y,n,q,a,d,j,J,g,/,e,p,?]? y
@@ -19,6 +22,7 @@
     </ProjectConfiguration>
   </ItemGroup>
   <ItemGroup>
+    <None Include="packages.config" />
     <None Include="ReadMe.txt" />
   </ItemGroup>
   <ItemGroup>
(2/3) Stash this hunk [y,n,q,a,d,K,j,J,g,/,e,p,?]? y
@@ -147,5 +151,15 @@
   </ItemGroup>
   <Import Project="$(VCTargetsPath)\Microsoft.Cpp.targets" />
   <ImportGroup Label="ExtensionTargets">
+    <Import Project="..\packages\Microsoft.Windows.SDK.CPP.10.0.26100.2454\build\native\Microsoft.Windows.SDK.cpp.targets" Condition="Exists('..\packages\Microsoft.Windows.SDK.CPP.10.0.26100.2454\build\native\Microsoft.Windows.SDK.cpp.targets')" />
   </ImportGroup>
+  <Target Name="EnsureNuGetPackageBuildImports" BeforeTargets="PrepareForBuild">
+    <PropertyGroup>
+      <ErrorText>This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them.  For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is {0}.</ErrorText>
+    </PropertyGroup>
+    <Error Condition="!Exists('..\packages\Microsoft.Windows.SDK.CPP.10.0.26100.2454\build\native\Microsoft.Windows.SDK.cpp.props')" Text="$([System.String]::Format('$(ErrorText)', '..\packages\Microsoft.Windows.SDK.CPP.10.0.26100.2454\build\native\Microsoft.Windows.SDK.cpp.props'))" />
+    <Error Condition="!Exists('..\packages\Microsoft.Windows.SDK.CPP.10.0.26100.2454\build\native\Microsoft.Windows.SDK.cpp.targets')" Text="$([System.String]::Format('$(ErrorText)', '..\packages\Microsoft.Windows.SDK.CPP.10.0.26100.2454\build\native\Microsoft.Windows.SDK.cpp.targets'))" />
+    <Error Condition="!Exists('..\packages\Microsoft.Windows.SDK.CPP.arm64.10.0.26100.2454\build\native\Microsoft.Windows.SDK.cpp.arm64.props')" Text="$([System.String]::Format('$(ErrorText)', '..\packages\Microsoft.Windows.SDK.CPP.arm64.10.0.26100.2454\build\native\Microsoft.Windows.SDK.cpp.arm64.props'))" />
+    <Error Condition="!Exists('..\packages\Microsoft.Windows.WDK.ARM64.10.0.26100.2454\build\native\Microsoft.Windows.WDK.arm64.props')" Text="$([System.String]::Format('$(ErrorText)', '..\packages\Microsoft.Windows.WDK.ARM64.10.0.26100.2454\build\native\Microsoft.Windows.WDK.arm64.props'))" />
+  </Target>
 </Project>
\ No newline at end of file
(3/3) Stash this hunk [y,n,q,a,d,K,g,/,s,e,p,?]? y

diff --git a/KMDF Driver1/KMDF Driver1.vcxproj b/KMDF Driver1/KMDF Driver1.vcxproj
index 6a4e8cf..8694853 100644
--- a/KMDF Driver1/KMDF Driver1.vcxproj
+++ b/KMDF Driver1/KMDF Driver1.vcxproj
@@ -1,5 +1,8 @@
 <?xml version="1.0" encoding="utf-8"?>
 <Project DefaultTargets="Build" ToolsVersion="12.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
+  <Import Project="..\packages\Microsoft.Windows.WDK.ARM64.10.0.26100.2454\build\native\Microsoft.Windows.WDK.arm64.props" Condition="Exists('..\packages\Microsoft.Windows.WDK.ARM64.10.0.26100.2454\build\native\Microsoft.Windows.WDK.arm64.props')" />
+  <Import Project="..\packages\Microsoft.Windows.SDK.CPP.arm64.10.0.26100.2454\build\native\Microsoft.Windows.SDK.cpp.arm64.props" Condition="Exists('..\packages\Microsoft.Windows.SDK.CPP.arm64.10.0.26100.2454\build\native\Microsoft.Windows.SDK.cpp.arm64.props')" />
+  <Import Project="..\packages\Microsoft.Windows.SDK.CPP.10.0.26100.2454\build\native\Microsoft.Windows.SDK.cpp.props" Condition="Exists('..\packages\Microsoft.Windows.SDK.CPP.10.0.26100.2454\build\native\Microsof:...skipping...
diff --git a/KMDF Driver1/KMDF Driver1.vcxproj b/KMDF Driver1/KMDF Driver1.vcxproj
index 6a4e8cf..8694853 100644
--- a/KMDF Driver1/KMDF Driver1.vcxproj
+++ b/KMDF Driver1/KMDF Driver1.vcxproj
@@ -1,5 +1,8 @@
 <?xml version="1.0" encoding="utf-8"?>
 <Project DefaultTargets="Build" ToolsVersion="12.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
+  <Import Project="..\packages\Microsoft.Windows.WDK.ARM64.10.0.26100.2454\build\native\Microsoft.Windows.WDK.arm64.props" Condition="Exists('..\packages\Microsoft.Windows.WDK.ARM64.10.0.26100.2454\build\native\Microsoft.Windows.WDK.arm64.props')" />
+  <Import Project="..\packages\Microsoft.Windows.SDK.CPP.arm64.10.0.26100.2454\build\native\Microsoft.Windows.SDK.cpp.arm64.props" Condition="Exists('..\packages\Microsoft.Windows.SDK.CPP.arm64.10.0.26100.2454\build\native\Microsoft.Windows.SDK.cpp.arm64.props')" />
+  <Import Project="..\packages\Microsoft.Windows.SDK.CPP.10.0.26100.2454\build\native\Microsoft.Windows.SDK.cpp.props" Condition="Exists('..\packages\Microsoft.Windows.SDK.CPP.10.0.26100.2454\build\native\Microsoft.Windows.SDK.cpp.props')" />
   <ItemGroup Label="ProjectConfigurations">
     <ProjectConfiguration Include="Debug|x64">
       <Configuration>Debug</Configuration>
@@ -19,6 +22,7 @@
     </ProjectConfiguration>
   </ItemGroup>
   <ItemGroup>
+    <None Include="packages.config" />
     <None Include="ReadMe.txt" />
   </ItemGroup>
   <ItemGroup>
@@ -147,5 +151,15 @@
   </ItemGroup>
   <Import Project="$(VCTargetsPath)\Microsoft.Cpp.targets" />
   <ImportGroup Label="ExtensionTargets">
+    <Import Project="..\packages\Microsoft.Windows.SDK.CPP.10.0.26100.2454\build\native\Microsoft.Windows.SDK.cpp.targets" Condition="Exists('..\packages\Microsoft.Windows.SDK.CPP.10.0.26100.2454\build\native\Microsoft.Windows.SDK.cpp.targets')" />
   </ImportGroup>
+  <Target Name="EnsureNuGetPackageBuildImports" BeforeTargets="PrepareForBuild">
+    <PropertyGroup>
+      <ErrorText>This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them.  For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is {0}.</ErrorText>
+    </PropertyGroup>
+    <Error Condition="!Exists('..\packages\Microsoft.Windows.SDK.CPP.10.0.26100.2454\build\native\Microsoft.Windows.SDK.cpp.props')" Text="$([System.String]::Format('$(ErrorText)', '..\packages\Microsoft.Windows.SDK.CPP.10.0.26100.2454\build\native\Microsoft.Windows.SDK.cpp.props'))" />
+    <Error Condition="!Exists('..\packages\Microsoft.Windows.SDK.CPP.10.0.26100.2454\build\native\Microsoft.Windows.SDK.cpp.targets')" Text="$([System.String]::Format('$(ErrorText)', '..\packages\Microsoft.Windows.SDK.CPP.10.0.26100.2454\build\native\Microsoft.Windows.SDK.cpp.targets'))" />
+    <Error Condition="!Exists('..\packages\Microsoft.Windows.SDK.CPP.arm64.10.0.26100.2454\build\native\Microsoft.Windows.SDK.cpp.arm64.props')" Text="$([System.String]::Format('$(ErrorText)', '..\packages\Microsoft.Windows.SDK.CPP.arm64.10.0.26100.2454\build\native\Microsoft.Windows.SDK.cpp.arm64.props'))" />
+    <Error Condition="!Exists('..\packages\Microsoft.Windows.WDK.ARM64.10.0.26100.2454\build\native\Microsoft.Windows.WDK.arm64.props')" Text="$([System.String]::Format('$(ErrorText)', '..\packages\Microsoft.Windows.WDK.ARM64.10.0.26100.2454\build\native\Microsoft.Windows.WDK.arm64.props'))" />
+  </Target>
 </Project>

The C driver samples repo also does something similar, albeit via director props override:
https://github.com/microsoft/Windows-driver-samples/blob/57ecdd5d16347ef3bc1348a164ce90288c44c243/Directory.Build.props#L1

I think maybe the best path forward here is for the nuget path to leverage the same env vars that the eWDK uses. It would be good if in the longterm, the nuget path better handles rust drivers, but for now we could provide instructions for setting the env var paths correctly. Ie. use this code path:

windows-drivers-rs/crates/wdk-build/src/utils.rs

Line 88 in 10a8e37

// If WDKContentRoot is present in environment(ex. running in an eWDK prompt),

svasista-ms added 30 commits October 2, 2024 20:01

Initial commit: use nuget pkgs

36b1d1e

Initial commit: use nuget pkgs

7e467f6

Merge branch 'microsoft:main' into port-pipeline

f04f22f

add NugetWDKContentRoot env variable detection to detect_wdk_content_…

b641096

…root

Merge branch 'port-pipeline' of https://github.com/svasista-ms/window…

6d024aa

…s-drivers-rs into port-pipeline

Add steps to install Nuget, move signtool to WDK's bin dir and set Nu…

d901e20

…getWDKContentRoot env variable

Add action to install Nuget

3038dc2

Add action to install Nuget

40441ad

Add action to install Nuget

80996e1

Add action to install Nuget

ffc24b3

Add action to install Nuget

e86b142

Fix condition to run Nuget installation

3922faf

Fix WDK version in the matrix

03f6633

Fix NuGet command

7343913

Add command to set NugetWdkContentRoot ENV VAR

13fd747

Add command to set NugetWdkContentRoot ENV VAR

9d1698d

Add command to set NugetWdkContentRoot ENV VAR

52e0ac7

Add command to set NugetWdkContentRoot ENV VAR

5e29f19

Add command to set NugetWdkContentRoot ENV VAR

1046cbf

Add command to set NugetWdkContentRoot ENV VAR

3b39c40

Replace x64 with ARM64 contents

dbc2f27

Replace x64 with ARM64 contents

edcbec9

List contents of WDK Root Dir

c0eeeb8

List contents of WDK Root Dir

9b9bb08

Add print stmts for debugging

4c5cb6e

Add print stmts for debugging

2e28af7

Add print stmts for debugging

860b337

Reduce matrix options for faster workflow exec

02e3fbd

Fix wdk tool root for nuget package - tools instead of Tools

abd946e

Replace ARM64 with x64 to match the host arch

a656057

svasista-ms added 11 commits October 10, 2024 21:21

Move certmgr to WDK bin directories

72e518d

Move MakeCert to respective WDK bin directories

efcb4db

Move nuget-install-wdk to separate script

2e3024f

Move nuget-install-wdk to separate script

98df970

Move nuget-install-wdk to separate script

30f4fa6

Enable WDK NI in the matrix

e156edd

Remove debug print stmts, Enable target triple, Use Tools/ instead of…

bf6203c

… tools/ for WDK tool root

Enable all profiles, toolchains, targets in the matrix; complete matr…

d3c0fad

…ix test

Enable other workflows

4df4330

Merge branch 'microsoft:main' into port-pipeline

a421cd7

Enable Latest WDK (uses NuGet) in all workflows

b8fdb0d

wmmc88 requested changes Oct 14, 2024

View reviewed changes

svasista-ms added 10 commits October 14, 2024 10:02

Revert to error handling using '?' for canonicalize and strip_extende…

41a7b7e

…d_length_path_prefix

Merge branch 'main' into port-pipeline

ccdb96a

Merge branch 'main' of https://github.com/microsoft/windows-drivers-rs …

f632131

…into port-pipeline

Remove NugetWdkContentRoot env var, add logic in nuget-install-wdk.ps…

d2e3a61

…1 script to install WDK version based on the matrix input, fix clippy issue

Merge branch 'port-pipeline' of https://github.com/svasista-ms/window…

beedcb0

…s-drivers-rs into port-pipeline

Update Install WDK (NuGet) step in other workflows

37b4bd6

Fix Install WDK (NuGet) script's condition in accordance to the power…

f4087df

…shell shell

Fix Install WDK (NuGet) script's condition in codeql.yml; Fix is_none…

a559f6d

…_or issue in utils.rs

change output directory of NuGet restore to C:\WDK

a350aa5

fix packagesConfigPath in nuget-install-wdk.ps1

5868673

svasista-ms changed the title ~~feat: enable CI workflows to use the latest NuGet WDK packages~~ feat: enable CI workflows to use NuGet WDK packages Oct 16, 2024

svasista-ms and others added 3 commits October 22, 2024 09:46

use is_none_or() for clippy::nominal_bool

a422a4c

remove unnecessary hashes around raw string literal

0256275

Merge branch 'main' into port-pipeline

058b784

NateD-MSFT reviewed Nov 27, 2024

View reviewed changes

NateD-MSFT approved these changes Nov 27, 2024

View reviewed changes

wmmc88 requested changes Dec 4, 2024

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: enable CI workflows to use NuGet WDK packages #236

feat: enable CI workflows to use NuGet WDK packages #236

svasista-ms commented Oct 14, 2024 •

edited

Loading

wmmc88 Oct 14, 2024

svasista-ms Oct 14, 2024

wmmc88 Oct 14, 2024 •

edited

Loading

NateD-MSFT Oct 14, 2024

wmmc88 Oct 14, 2024

NateD-MSFT Nov 27, 2024

wmmc88 Nov 27, 2024

wmmc88 Dec 3, 2024

wmmc88 Dec 3, 2024

wmmc88 Dec 3, 2024

wmmc88 Dec 4, 2024

NateD-MSFT Dec 5, 2024

wmmc88 Dec 5, 2024 •

edited

Loading

NateD-MSFT Dec 5, 2024

wmmc88 Dec 4, 2024

wmmc88 Dec 4, 2024

wmmc88 Dec 4, 2024

wmmc88 Dec 4, 2024

svasista-ms Dec 5, 2024

wmmc88 Dec 5, 2024

wmmc88 commented Dec 4, 2024 •

edited

Loading

feat: enable CI workflows to use NuGet WDK packages #236

Are you sure you want to change the base?

feat: enable CI workflows to use NuGet WDK packages #236

Conversation

svasista-ms commented Oct 14, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

wmmc88 Oct 14, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

wmmc88 Dec 5, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

wmmc88 commented Dec 4, 2024 • edited Loading

svasista-ms commented Oct 14, 2024 •

edited

Loading

wmmc88 Oct 14, 2024 •

edited

Loading

wmmc88 Dec 5, 2024 •

edited

Loading

wmmc88 commented Dec 4, 2024 •

edited

Loading