Bjarne

Thanks to @FelixWorkspace for telling me that this is in fact a problem on Microsoft's site and not an error in my implementation. See the following issue in the winget-cli...

Thank you for the information, we probably need to wait for this problem to be fixed in WinGet but I will take a look at it too.

I have added an alternative exact method for getting installed packages, without using WinGet’s exact functionality as a workaround for this issue. https://github.com/basicx-StrgV/WGet.NET/releases/tag/4.2.0

I’m closing the issue for now. If there are still Problems with this or anything else, feel free to open another issue.

I will release a patch that should fix this and other current issues as soon as possible.

I released a patch (Version 4.1.1) containing a fix for this issue. https://github.com/basicx-StrgV/WGet.NET/releases/tag/4.1.1

Thank you for the suggestion. I will play around with the idea when I have the time, but can’t guarantee that the functionality will ever be implemented. I will update...

I’m currently testing SSH implementation for remote execution. If this turns out to work well, it will be implemented as a feature for the library.