microsoft / microsoft/winget-pkgs

[Package Request]: Microsoft.AppInstaller.Preview

Open
#408,567 0 comments 0 reactions 0 assignees View on GitHub
Help-Wanted Needs-Triage Package-Request
Dominant language
No language data
Stars
11.1k
Forks
9.7k
Avg merge
1h 32m
Merged PRs (30d)
616

Description

### How can we help?

I would like someone else to build the manifest.

### Please read and ensure the following

- [x] The installer meets the above requirements

### Please provide the following information

Download Page Url: https://github.com/microsoft/winget-cli/releases
Publisher: Microsoft Corporation
Package Name: App Installer (Preview)
Description: The preview builds of App Installer, which simplifies the installation of Windows applications by allowing users to sideload app packages with a double-click—no need to run PowerShell scripts or command-line tools.
Package Version: 1.30.70(.0)
Installer Url: https://github.com/microsoft/winget-cli/releases/download/v1.30.70-preview/Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle
——————————————————————————
Notes from me:
* Though it would probably be pretty high up on lists of "Apps that would fit well in winget-pkgs", I admit it's not straightforward to just add it. Due to how the winget-cli releases are currently built, the preview builds share the same PackageFamilyName as the stable `Microsoft.AppInstaller`, which would cause problems with a capital P unless some good idea gets cooked up in some form. Simply removing PackageFamilyName should have worked on paper, but ran into #404742.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the existing stable Microsoft.AppInstaller manifest and the release asset at the provided installer URL. Read issue #404742 to understand the PackageFamilyName problem, then determine whether the preview manifest can coexist with the stable package; done means the manifest builds without that conflict.

Written by the indexing model from the issue text.

Assessment

Domain
cli, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.