search

PowerShellCrack / WinGetWrapperModule

A wrapper around winget command line utility without using colbalt or third party
MIT License
1 stars 0 forks source link

Modules #1

Open DannyJanmaat opened 1 month ago

DannyJanmaat commented 1 month ago

Hello,

A lot of modules are not working correctly or does not catch all possible problems.

I would not use this till these problems are solved.

Get-WinGetWrapperList does not have a clean output/ Test-IsWinGetInstalled is to basic, it can also check for winget within WindowsApps for example. etc. etc. etc.

PowerShellCrack commented 1 month ago

Thanks for the feedback. I am aware of the issues; when this was released, it worked great. However winget output is constantly updating. Since winget output is text, it can be difficult to break it up into objects.

I will take some time to look into it, but I wouldn't get your hopes up. Are you needing a winget module?

DannyJanmaat commented 1 month ago

I already have it working. However, I strongly advice people to use the much faster Microsoft.Winget.Client module

$M = "Microsoft.Winget.Client" Install-Module $M -Fo Import-Module $M

The only reason I need it without installing any modules is because I have to automate it to install apps while ESP via AutoPilot deployment.

You can easily cleanup the output to use a regex expression against to replace all special characters except '.' and not for the name. Then you can use the Id of that output to keep it against the 'winget show' command and have all the necessary values needed.

PowerShellCrack commented 1 week ago

Oh 100% use Microsoft.Winget.Client. This was a concept one to see if it can be done via direct PowerShell and no dlls. I will be sure to note that in the readme just to be clear.

DannyJanmaat commented 1 week ago

If you still want to get this working then to create the custom objects you need to match the spacing of the header items for the returned objects.