Closed asilverman closed 1 year ago
I think the main challenge currently is the release artifacts are NuGet packages rather than an "installer" or a "portable" application.
Yes, it would be great to simplify dev setup. Currently, we have developers install the SDK with:
winget install -e --id Microsoft.DotNet.SDK.6 -v 6.0.403
It would be great if we could do something similar to:
winget install --id Microsoft.ArtifactsCredProvider
This would save a lot of developer time.
@cataggar , @grubyhs, @asilverman The team are extremely ruthless with closing tickets without upvotes. I'd highly recommend upvoting & commenting on the following item so we can actually get some traction on alternate deployment options.
https://developercommunity.visualstudio.com/t/Add-Windows-installer-options-for-Azure/10308779
In order to consolidate to fewer feedback channels, we've moved suggestions and issue reporting to Developer Community.
Overview
The winget command line tool enables users to discover, install, upgrade, remove and configure applications on Windows 10 and Windows 11 computers. This tool is the client interface to the Windows Package Manager service. (For more information see here
Currently the process of installing & updating artifacts-credprovider is a bit challenging and requires active user interaction. Using winget to install and update would be a much nicer and easier experience and would allow users to benefit from using the latest version with the latest fixes.
To add artifacts-credprovider to winget is simple, just add to CI/CD pipeline a task per the following documentation. If you need more information you can also contact @denelon for help
Benefits
Often times artifacts-credprovider is one of the dev setup dependencies and having an easy way to winget it would make it easier to onboard and ensure that developers can spin a dev environment quickly