@apxltd Thanks for the update. I really appreciate you taking the time

The reason I was looking to see if you supported winget yet is that I was replacing my own machine and I like to rebuild our developer image as I do so. I build our image from a base Windows image that has current Windows. I then run the “winget install” scripts to install the common tool chain.

I understand on your side it doesn’t seem like a workable solution, but I love it. Winget works as if I downloaded and installed all the installs manually. Then I can just run “winget upgrade” to see what needs to be upgraded.

The main benefit is that the upgrade check works even if a developer or I install something without using winget to install it. This is because “winget upgrade” uses Windows installed apps (as seen in appwiz.cpl) for its check.

I hope they cleanup the backend so you could look at this product again.

@apxltd Sorry I missed your reply. We are a company of 50+ developers. We currently use ProGet for npm, nuget, docker and maven. It works great.

We have used Chocolately in the past, but moved to WinGet as it is part of the OS and like how it integrates with Windows more seamlessly. This may have changed, but we didn't like how Chocolately had a separate catalog of what was installed and installed certain items in Chocolately folders. This often caused issues finding where command line utilities were installed as they were not in their "default/google-able" location.

What we would like to have available is download caching. It would be nice have the second and later people installing a multi GB install download it from the LAN vs 50 workstations downloading it from the internet.

@sylvain-martel_3976 Please add a feed for winget. It is the first party tool from MS and has the benefit of being "in the box". It has come a long way since 2021 and we use it exclusively.