Add alternative version number field to manifest to make correlation with entries in Add/Remove programs more reliable

[chausner]

Description of the new feature/enhancement

As reported here, the winget upgrade command may incorrectly detect updates to be available even when the latest version is installed in case the version number in Add/Remove programs does not match the package version in the manifest.

One solution to this problem could be the addition of an additional version field to the manifest where the version number is specified in the format that is expected in Add/Remove programs. When present, the winget upgrade routine would use this version number instead of the package version to determine if an update is available or not.

This suggestion is closely related to microsoft/winget-pkgs#13620.

[denelon]

@chausner we have another issue in the client I think this is a duplicate of #976.

Edit: I didn't read fully.

[denelon]

I moved this to be a feature in the client.

[denelon]

This is part of the work we're doing with the new schema. We have added a section for data specifically matching what is reported via Apps & Features.

[denelon]

Related to:

• Improve package matching against Apps & Features Entry #1952
• Schema extension to support multiple ARP entries. #1073

[denelon]

We're going to use this Issue to represent the work to start looking at the version in the AppsAndFeatures section of the manifest (if it is populated) rather than the PackageVersion for version comparison.

PackageVersion:         # Used for version comparison if no DisplayVersion key is present
- AppsAndFeatures
    DisplayVersion:     # Used for version comparison if the key is present

[denelon]

When we have an installed package and the manifest in the repository uses the AppsAndFeatures version we need a rational way to display the "somewhat unknown" "displayVersion" to the user.

The example below is contrived, but is intended to illustrate the syntax we're considering using.

We're thinking of using "> " for the winget list scenario where the user has a newer version installed.

Name           Id                   Version   Available Source
------------------------------------------------------------
Git            Git.Git              > 2.36.0            winget
GitHub Desktop GitHub.GitHubDesktop 2.9.15    3.0.0     winget

We're thinking of using "< " for the winget upgrade scenario where the users has an older version installed, but it doesn't match an existing manifest.

Name           Id                   Version   Available Source
------------------------------------------------------------
Git            Git.Git              < 2.36.0  2.36.0    winget
GitHub Desktop GitHub.GitHubDesktop 2.9.15    3.0.0     winget