Setup releases to publish to choco and/or winget package managers about artifacts-credprovider HOT 9 OPEN

Not stale.

from artifacts-credprovider.

I had mentioned something similar in #370 but they won't accept feature requests here.

If you would like to upvote/comment on the following it might help get some attention:
https://developercommunity.visualstudio.com/t/Add-installer-options-for-Azure-Artifact/10308779

from artifacts-credprovider.

We're no longer forwarding to the developer community, so having issues here is appropriate.

from artifacts-credprovider.

@JohnSchmeichel , great another overnight change :), so the two issues that were closed #370 and #379 can be added to this request. I'll reiterate my comments here.

An installer or winget package would help deployment at a larger scale though services like InTune or other software management tools.
This might be an MSI, Exe or winget based deployment options.

At the moment the only installation options are a Zip of un-trusted PS scripts.

from artifacts-credprovider.

This issue has had no activity in 90 days. Please comment if it is not actually stale.

from artifacts-credprovider.

This issue has had no activity in 90 days. Please comment if it is not actually stale.

from artifacts-credprovider.

🙄

from artifacts-credprovider.

It seems like this should be possible now in winget now that Windows Package Manager manifests allow portable zip, although I can't tell at first glance if the zip must contain an installer or if the contents can just be extracted into a directory directly as the "installation."

from artifacts-credprovider.

I just linked a PR in winget-pkgs to this issue that takes a crack at integrating into winget, but the standalone zip with lack of an installer (WiX/Nullsoft/etc.) seems to make it unable to be fully automatic with winget; the install location can't be preset to the NuGet plugin directory, or if this can be set in the manifest I couldn't tell what YAML property would do it.

And I guess requiring the --location argument to be specified manually on install is preventing the PR build validation from succeeding, but the failure in the PR build is opaque so I'm not sure.

Update: the issue appears to be due to the default symlinking winget does to add the CredentialManager.Microsoft.exe to the PATH and the test case of launch the console app via the PATH symlink fails due to inability to find dependent DLLs (the DLL loading algorithm doesn't use the actual location of the exe as the DLL search path). That said, there seems to be no mechanism to just "extract the zip here and don't add it to PATH" in winget.

from artifacts-credprovider.