« Previous 1 2 3 4
Package management tools for Windows
Unboxing
Conclusions
One solution I did not discuss in this article is Scoop [10], which takes the approach of allowing installations in the user context (and therefore also in the user profile) and mutually isolating the packages to the extent possible. This naturally limits the selection of available applications slightly, but at the same time it helps the potential user base grow.
If you want to establish full-fledged package management on Windows, you basically have a choice between Chocolatey and Microsoft's own WinGet. If you want to manage the application zoo on your own servers, you are far better off with Chocolatey, but you need your own repository and package quality assurance procedure. WinGet, on the other hand, gives your clients access to Microsoft-approved repositories and can address a private repository, if needed, but you have to build it yourself, which involves substantial overhead. If you want to track the lifecycle of packages across your entire infrastructure, Chocolatey for Business is the best choice.
Infos
- Chocolatey: https://chocolatey.org
- WinGet in Docs: https://learn.microsoft.com/en-US/windows/package-manager/
- AppGet announcement: https://keivan.io/appget-what-chocolatey-wasnt/
- Microsoft comments on WinGet and AppGet: https://devblogs.microsoft.com/commandline/winget-install-learning/
- In-house repositories for Chocolatey: https://docs.chocolatey.org/en-us/features/host-packages
- WinGet on Server 2022: https://www.andreasnick.com/112-install-winget-and-appinstaller-on-windows-server-2022.html
- Microsoft: Private WinGet resources: https://github.com/microsoft/winget-cli-restsource
- GitHub Foil repository: https://github.com/ethanbergstrom/Foil
- winget-create: https://github.com/microsoft/winget-create
- Scoop: https://scoop.sh
« Previous 1 2 3 4
Buy this article as PDF
(incl. VAT)