You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first step into AppsAndFeaturesEntries we can take is probably clearing and prompting for the DisplayVersion under AppsAndFeaturesEntries IF its defined
Once winget-cli and wingetcreate actually supports manifest schema 1.1.0 we can probably move the ProductCode to AppsAndFeaturesEntries
I think that we may want to address how we handle version detection as a whole.
Theres probably a few parts to this:
Remove the version input at the beginning
Find the latest version of the app inside the app folder
Make display version key mandatory for the first installer. Have a suggested value as the one defined by the downloaded installer file if it exists. If it is not the first installer, it should be optional, but if not entered it will take the same value as the first installer.
If all display versions are the same and are not null or empty strings, use that as the package version. Otherwise, ask the user to input the package version
Description of the new feature/enhancement
Test manifest/reference manifest: AnyDeskSoftwareGmbH.AnyDesk (not direct link since it may change)
The first step into
AppsAndFeaturesEntries
we can take is probably clearing and prompting for theDisplayVersion
underAppsAndFeaturesEntries
IF its definedOnce
winget-cli
andwingetcreate
actually supports manifest schema 1.1.0 we can probably move theProductCode
toAppsAndFeaturesEntries
Proposed technical implementation details (optional)
No response
The text was updated successfully, but these errors were encountered: