4 ms·
Great. So now we have: * MSI * EXE * MSU * AppX * Windows Features * dism * Windows Update * SCCM Deployments * MSIX. So now everyone uses MSIX? Or are there
by aboringusername 6y ago
Great. So now we have:
* MSI * EXE * MSU * AppX * Windows Features * dism * Windows Update * SCCM Deployments * MSIX.
So now everyone uses MSIX? Or are there still a combination of all of the above being used today?
Creating a new standard is one thing, enforcing it is another. It's like XKCD 927, just yet another option to add to the list.
[1]: https://xkcd.com/927/ https://xkcd.com/927/
- naikrovek 6y agoOh God, choice! Options! They're so awful! Why don't Microsoft force one standard on everyone, so we can complain about a lack of options instead of complaining about having too many options? Why are multiple options a bad thing? Seriously.
- aksss 6y agoYou forgot about Microsoft InTune.. basically cloud-based SCCM. It has its own packager as well. Basically wraps up MSIs. https://github.com/Microsoft/Microsoft-Win32-Content-Prep-Tool https://github.com/Microsoft/Microsoft-Win32-Content-Prep-To...
- fomine3 6y agoNot to forget ClickOnce!
- 2fast4you 6y agoCan we add “Windows Optional Features” to that list? It’s basically “Windows Features”, except everything has a different name