Skip to content

Integrate Pinget for WinGet operations#4665

Merged
Gabriel Dufresne (GabrielDuf) merged 1 commit intomainfrom
pinget
Apr 30, 2026
Merged

Integrate Pinget for WinGet operations#4665
Gabriel Dufresne (GabrielDuf) merged 1 commit intomainfrom
pinget

Conversation

@mamoreau-devolutions
Copy link
Copy Markdown
Contributor

Summary

  • replace the bundled WinGet CLI path with a bundled Pinget CLI fallback
  • use Devolutions.Pinget.Core 0.3.0 for structured WinGet package metadata
  • add WinGet COM and command-line tool selection settings, environment overrides, UI entries, and tests

Validation

  • dotnet restore .\src\UniGetUI\UniGetUI.csproj /p:Platform=x64 --nologo
  • dotnet build .\src\UniGetUI\UniGetUI.csproj --framework net10.0-windows10.0.26100.0 --configuration Debug /p:Platform=x64 --no-restore --nologo
  • dotnet test .\src\UniGetUI.PackageEngine.Tests\UniGetUI.PackageEngine.Tests.csproj --configuration Debug /p:Platform=x64 --nologo --filter "FullyQualifiedName~WinGet"

Notes: build has the existing CA1822 warning in Updates.xaml.cs; the WinGet-filtered test run passes 45 tests on the Windows target and reports no matches on the plain net10.0 target.

Replace the bundled WinGet CLI path with a bundled Pinget CLI fallback and use Devolutions.Pinget.Core for structured package metadata.

Add settings and environment controls for WinGet COM usage and command-line tool selection, wire the new UI options, and update WinGet manager tests for the new behavior.
@GabrielDuf Gabriel Dufresne (GabrielDuf) merged commit 5d8de3c into main Apr 30, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants