WinGet becomes a DSC v3 resource

[denelon]

Description of the new feature / enhancement

I want to be able to configure WinGet without needing to download a PowerShell DSC resource.

PowerShell DSC v3 enables an application written in any language to be it's own DSC Resource.

Related to:

• Experimental support for DSC v3 preview #3676

Proposed technical implementation details

Implement the PowerShell DSC v3 Resource interface into WinGet.

[denelon]

Related discussion:

• Implementing DSC v3 in a few Windows developer tools. PowerShell/DSC#664

[denelon]

This feature is now experimental using the "configureExport" experimental feature.

Note

There are some manual steps required as of WinGet 1.11.320-preview

The WinGet resource.json files need to be available on the path. The example below will add the files in your user directory and add your user directory to the user path.

cd ~
winget dscv3 --manifest -o C:\Users\<your user name>
[Environment]::SetEnvironmentVariable("PATH", $env:PATH + ";$(Get-Location)", [EnvironmentVariableTarget]::User)