Hacker News Reader

Comment by hypercube33 | Hacker News Reader

You can tell by WinGet which is a new product not even close to supporting anything PowerShell by design and almost being anti PowerShell with its overly verbose output. Which is odd since it's right up powershells alley being a management cli tool

View on HN

If you have winget and powershell installed, try `Get-WingetPackage` and see what comes out. Or even better:

    gcm | ? noun -like winget*
    help Install-WinGetPackage

The "usual" winget cli tool is indeed not powershell compatible. But winget also ships with all the necessary cmdlets. You don't have to install anything extra.

I was super excited to see this comment, but I don't seem to have those cmdlets, even though I'm on Windows 11, fully updated. Are you sure you didn't install something extra?

If I recall correctly, they only work in PowerShell 7. If you don’t even have them in there, you can install them from https://github.com/microsoft/winget-cli (which is bad UX, but if you just need them on one system it’s a way to do it).

I'm in PowerShell 7.4.2 and they're definitely absent. I hadn't thought to install directly from GitHub, given part of the whole shtick of winget is it's The One True Package Manager and bundled, but I can't say I'm surprised, either...

Probably better off installing from PowerShell Gallery instead. https://www.powershellgallery.com/packages/Microsoft.WinGet....

I don't remember. Maybe I did install the modules. https://www.powershellgallery.com/packages/Microsoft.WinGet....

    Install-Module -Name Microsoft.WinGet.Client

The Winget module is a wreck. The way it is designed, unfortunately, neither fits the object oriented approach of PowerShell nor follows the PowerShell guidelines for cmdlets.

For instance https://github.com/microsoft/winget-cli/issues/3820 or https://github.com/microsoft/winget-cli/issues/3231.

Also, even though it does not completely work with PowerShell 5, it is marked as compatible. https://github.com/microsoft/winget-cli/issues/2881

The design choices made makes it weird. I hope it would be a good one in the future. But it is now problematic.

There is a Winget client module for Powershell. I used it the other day to write a one liner that could upgrade all with exclusions. I didn't want to pin, because I still wanted to see updates I'm skipping.

Does anyone even use winget? I tried but its repositories never have the tools I need in it. Scoop has been superior for me in every way.

UniGetUI (formerly WingetUI) is a really great tool since it supports multiple package managers.

https://github.com/marticliment/UniGetUI

I have found it useful. I used to install PowerShell 7.x, kubectl, Bicep (Azure language for deploying resources), etc. It works fine. The biggest problem I have is I cannot use it to install helm because the helm package is not shipped by the helm team (I don't trust packages shipped by third parties).

Yeah for the things they have its great, I've just found that they lack a lot of stuff. To this day they still don't have Apache Maven in the repository. I just use scoop, I've found that its repositories just have way more tools and it's way easier to contribute to.

Have you asked the Helm team why they don't ship their own package? It might be worth the effort.

I'm personally trying to use it inside configman running as SYSTEM and have gotten it working for the most part but I have not seen anything module based from Microsoft themselves.

Yes what I am doing can be done with intune but that's another story for another time. RIP Store for Business. I just want to deploy PowerBI and have it always be current and self updating.

Reply on news.ycombinator.com