wingetcreate is disappointing

[OfficialEsco]

wingetcreate is disappointing from what it sounded like it should have been..

What i like

• wincreate new will detect the InstallerType automatically
• wincreate new will suggest pretty good metadata

What i don't like

• wingetcreate is not user-friendly
• wingetcreate feels weird, why is it not winget create?
• wingetcreate new give way too few questions
• wingetcreate update --id does... nothing? if the manifest does not use a dynamic url. if -v -u -s is not inputted it should prompt for the information.
• wingetcreate update does not prompt to update any of the information
• wingetcreate update should change the InstallerType and SilentSwitches if it detects a compatible InstallerType
• wingetcreate update does not update the ProductCode and will keep the previous one like wingetbot.

I will be sticking to YamlCreate.ps1

[denelon]

@OfficialEsco lots to unpack here 😊. Thanks for the feedback!

Re: "wingetcrate vs winget create".
One of the use cases is a standalone tool for CI scenarios to help automate publishing manifests. We do plan on integrating this tool so you can "winget create" with this tool. microsoft/winget-cli#989

[denelon]

#20

wingetcreate update should change the InstallerType and SilentSwitches if it detects a compatible InstallerType

[denelon]

#22

wingetcreate update does not update the ProductCode and will keep the previous one like wingetbot.

[denelon]

#23
wingetcreate update does not prompt to update any of the information

[denelon]

#24
wingetcreate update --id does... nothing? if the manifest does not use a dynamic url. if -v -u -s is not inputted it should prompt for the information.

[OfficialEsco]

Oke, wingetcreate new just added fuel to the fire by ruining manifests with tons of metadata

[denelon]

@OfficialEsco thanks for the notes on microsoft/winget-pkgs#14621. Clearly we've got some work to do.