Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PowerShell DSC Resources for WinGet #2697

Open
denelon opened this issue Nov 14, 2022 · 2 comments
Open

PowerShell DSC Resources for WinGet #2697

denelon opened this issue Nov 14, 2022 · 2 comments
Labels
Issue-Feature This is a feature request for the Windows Package Manager client.

Comments

@denelon
Copy link
Contributor

denelon commented Nov 14, 2022

Description of the new feature / enhancement

I would like to be able to use PowerShell DSC to install and configure WinGet.

Several issues have made mention to challenges associated with getting WinGet installed (or in a valid state) on different Windows SKUs or environments:

@cdhunt also made a PR with a PowerShell script to help with this challenge:

A couple of mentions have also suggested PowerShell DSC:

Proposed technical implementation details

As we are nearing the first release of WinGet PowerShell modules and cmdlets, this would be aligned with that same effort.

@denelon
Copy link
Contributor Author

denelon commented Feb 27, 2023

Naming things is hard:

@denelon
Copy link
Contributor Author

denelon commented Mar 7, 2023

We should consider the options for making this work in the System context in terms of getting "WinGet" on the system, and then when the user logs in, the actual "registration" for the user is "faster".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature This is a feature request for the Windows Package Manager client.
Projects
None yet
Development

No branches or pull requests

1 participant