Update: Microsoft.WingetCreate version 1.1.2.0

[russellbanks]

• Have you signed the Contributor License Agreement?
• Have you checked that there aren't other open pull requests for the same manifest update/change?
• Have you validated your manifest locally with winget validate --manifest <path>?
• Have you tested your manifest locally with winget install --manifest <path>?
• Does your manifest conform to the 1.1 schema?

This adds the portable wingetcreate exe

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

Hello @russellbanks,
The package manager bot determined that the metadata was not compliant.

Please verify the manifest file is compliant with the package manager 1.0 manifest specification.
Make sure the ID is of the form publisher.appname and that the folder structure is manifests\partition\publisher\appname\version.
Note: The path and "PackageIdentifier" are case sensitive.
Be sure to use a tool like VSCode (https://code.visualstudio.com/) to make sure the manifest YAML syntax is correct.

You could also try our Windows Package Manager Manifest Creator Preview.

For details on the specific error, see the details link below in the build pipeline.

Template: msftbot/validationError/manifest/metadata

[ghost]

Hello @russellbanks,
The package manager bot determined changes have been requested to your PR.

Template: msftbot/changesRequested

[Trenly]

As I've been thinking. . . @ryfu-msft / @denelon - Given that this package is managed by the winget team, do you want the portable exe added here?

[denelon]

I've been thinking about this one since we have the MSIX version and the portable versions with and without dependencies to support CI/CD flows. We don't have anything like winget install <package> --installer-type [MSIX, MSI, .exe, portable, zip]. This is likely to set a precedent so we should be intentional.

[denelon]

We should look at:

• Specify InstallerType winget-cli#1166

[russellbanks]

It might make sense to have Microsoft.WingetCreate.Portable and break that down into the versions with and without dependencies. The manifest for the .exe without dependencies should declare them so if they are on the system they don't get downloaded.

Haven't the self-contained portable .exe's been removed since v1.1.2.0:

Note: Self-contained exes have been removed since WS2022 now supports AppExecutionAliases. Check out the README for instructions on how to use the msixbundle in your CI/CD pipeline.

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

Hello @russellbanks,
The package manager bot determined that the metadata was not compliant.

Please verify the manifest file is compliant with the package manager 1.0 manifest specification.
Make sure the ID is of the form publisher.appname and that the folder structure is manifests\partition\publisher\appname\version.
Note: The path and "PackageIdentifier" are case sensitive.
Be sure to use a tool like VSCode (https://code.visualstudio.com/) to make sure the manifest YAML syntax is correct.

You could also try our Windows Package Manager Manifest Creator Preview.

For details on the specific error, see the details link below in the build pipeline.

Template: msftbot/validationError/manifest/metadata

[denelon]

I think I'm OK having both the MSIX and the portable .exe in the same manifest. It's going to take feature work to allow someone to install the portable though. It might be best in the short term to have a Microsoft.WingetCreate.Portable manifest for now so people can use winget to install the portable version.

[denelon]

@ryfu-msft let me know if you have a different opinion 😊

[Trenly]

@wingetbot run

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

Hello @wingetbot!

Because this pull request has the Validation-Completed label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

[ghost]

Hello russellbanks,
Validation has completed.

Template: msftbot/validationCompleted