New package: Microsoft.VisualStudioCode.CLI version 1.80.0

[mdanish-kh]

• Have you signed the Contributor License Agreement?
• Have you checked that there aren't other open pull requests for the same manifest update/change?
• This PR only modifies one (1) manifest
• 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.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

• Resolves [Package Request]: Visual Studio Code CLI #111729

---

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[stephengillie]

Manual Validation ended with:

No installation of Visual Studio Code Stable was found. Install it from https://code.visualstudio.com and try again. If you already installed Visual Studio Code and we didn't detect it, run code version use stable --install-dir /path/to/installation

Should VSC Stable be a dependency?

[stephengillie]

@lszomoru, do you approve?

[cglong]

Per the VSCode documentation:

As you may need to run the CLI on a remote machine that can't install VS Code Desktop, the CLI is also available for standalone install on the VS Code download page.

Will wait for confirmation on this from @lszomoru 🙂

[lszomoru]

VS Code packages (Stable/Insiders) are being published to winget through automation. While we could manually publish this one package for the CLI, I do not believe that it would be the right approach as it would quickly become out of date. The right thing to do here, is for me to update our automation so that we start publishing packages for the CLI as well.

Filed microsoft/vscode#187634

[mdanish-kh]

[Policy] Area-External
[Policy] Blocking-Issue

[stephengillie]

Closing PR in favor of upstream pushes.