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

[New Feature]: Update WinGet to use UI.XAML 2.8 #3380

Closed
denelon opened this issue Jun 26, 2023 · 6 comments
Closed

[New Feature]: Update WinGet to use UI.XAML 2.8 #3380

denelon opened this issue Jun 26, 2023 · 6 comments
Labels
Issue-Feature This is a feature request for the Windows Package Manager client.
Milestone

Comments

@denelon
Copy link
Contributor

denelon commented Jun 26, 2023

Description of the new feature/enhancement

Keeping dependencies current is generally a good idea.

It would also help resolve:

Proposed technical implementation details (optional)

No response

@denelon denelon added the Issue-Feature This is a feature request for the Windows Package Manager client. label Jun 26, 2023
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage Issue need to be triaged label Jun 26, 2023
@denelon denelon removed the Needs-Triage Issue need to be triaged label Jun 26, 2023
@denelon denelon transferred this issue from microsoft/winget-pkgs Jun 26, 2023
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage Issue need to be triaged label Jun 26, 2023
@denelon denelon removed the Needs-Triage Issue need to be triaged label Jun 26, 2023
@A9G-Data-Droid
Copy link

Question: Why would a command line utility call anything from UI.Xaml?

Statement: A package manager needs to be able to run without any libraries or dependancies because that package manager is used to manage all libraries and dependencies. Consider making it self-contained.

@florelis
Copy link
Member

florelis commented Jul 6, 2023

Why would a command line utility call anything from UI.Xaml?

It doesn't. But winget is packaged along DesktopAppInstaller (the UI that shows up when you double-click on an .msix/.msixbundle), which has a dependency on WinUI 2.7.

@A9G-Data-Droid
Copy link

That seems like an odd choice for a package manager that might be running on a headless server.

These should be two completely different workflows:

  1. Using DesktopAppInstaller to install
  2. Using WinGet to install

When using workflow 2 I would expect all interaction to happen on the command line. Now on a system that has a desktop installed it would make sense for WinGet to be able to automatically install the DesktopAppInstaller when any package needs it, just like any other dependency.

@Trenly
Copy link
Contributor

Trenly commented Feb 28, 2024

@denelon - This has been completed?

@denelon denelon added this to the 1.8 Client milestone Mar 6, 2024
@denelon denelon closed this as completed Mar 6, 2024
@huuub
Copy link

huuub commented May 23, 2024

This problem is back... I installed xaml 2.8.6 but it needs 2.8???

@huuub
Copy link

huuub commented May 23, 2024

I am using this as a workaround:
$progressPreference = 'silentlyContinue'
Write-Information "Downloading WinGet and its dependencies..."
Invoke-WebRequest -Uri https://aka.ms/getwinget -OutFile Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle
Invoke-WebRequest -Uri https://aka.ms/Microsoft.VCLibs.x64.14.00.Desktop.appx -OutFile Microsoft.VCLibs.x64.14.00.Desktop.appx
Invoke-WebRequest -Uri https://github.com/microsoft/microsoft-ui-xaml/releases/download/v2.8.6/Microsoft.UI.Xaml.2.8.x64.appx -OutFile Microsoft.UI.Xaml.2.8.x64.appx
Add-AppxPackage Microsoft.VCLibs.x64.14.00.Desktop.appx
Add-AppxPackage Microsoft.UI.Xaml.2.8.x64.appx
Add-AppxPackage Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle

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

5 participants