Hacker News new | past | comments | ask | show | jobs | submit login

Imagine the difference between software distributed as a tarball and the binary package. Both totally work, but one is so much easier to deploy in bulk. (This is obviously a very loose analogy, but I think it's roughly correct)



Exe installers support unattended, headless installs with a command line switch.


But how you do run that command only once on every computer? Including ones that are currently not in the building, or on.


Same way as anything, use group policy or a login script that checks first.


But how do you know if it's installed correctly?


What does correctly mean? On windows usually a registry key is checked.


Exactly, changes from software to software. And how to uninstall?

Much easier to add an MSI to GPO, and then just as easy to remove it again and it's uninstalled.

Not sure how writing scripts to do all that myself for every piece of software is better.


Msi is deprecated.


So you keep saying, although don't see any evidence for it. MS want you to move to using the MS Store, because that's not terrible. Or manually download multiple files, put them all in specific places and use a powershell script to install it, hah, so easy.

MSIX is just a wrapper around an msi, exe, etc installer anyway.

In conclusion, just make an MSI file, they're much better, look at all these great features https://en.wikipedia.org/wiki/Windows_Installer




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: