4 ms·
To be fair, I think Microsoft considered Installers a Windows "bug" for many years. Installers have always been a problem on Windows and Microsoft has always t
by WorldMaker 7y ago
To be fair, I think Microsoft considered Installers a Windows "bug" for many years.
Installers have always been a problem on Windows and Microsoft has always treated it as the unfortunate problem child it was. A lot of guidance from Microsoft has been "avoid Installers [because you shouldn't need Registry settings, shouldn't be putting things in C:\Windows\System32, etc] and don't use things that need Installs, but if you do need an installer, here's MSI which is super complex, not least of which because the preferred tool to build MSI has only recently changed to an XML-based build tool from a crufty collection of worse command line tools and direct binary manipulation".
Then Microsoft tried too fast to move everyone to AppX as the One True Installer. But they forgot backwards compat and the slow pace of Enterprise. So now they are working to turn the ship on AppX with the rebrand/rebuild to MSIX (now with Windows 7+ support in preview), and this time trying to get more of the Traditional GUI Installer Builders in on the game (so that Enterprises with InstallShield licenses dating back to their VB3-based Windows 3.1 apps don't have to learn anything new).
MSIX seems to be a great solution to move forward with, but yes the road to get there has been really painful, and the damage of how many people are still using Installer Builder systems built only with Windows 95 in mind rather than anything more recent is a painful legacy that Windows will likely be hurting from for a long time.
- danmaz74 7y ago> To be fair, I think Microsoft considered Installers a Windows "bug" for many years. And that's the cusp of the problem. A really developer friendly company would have given a simple solution to a developer who had finished his product and wanted to distribute it!
- WorldMaker 7y agoThey certainly tried to make things better at times, though, they just often didn't have all the answers or solve the problem for enough use cases. ClickOnce had some good ideas, but the implementation lacked some details and the .NET-only focus left a lot of developers out. It's also why I find it funny that a lot of developers are so angry at Microsoft for the effort put into the Microsoft Store. They absolutely wanted to make the installer/deployment world a lot better for the average user. Sure, the Microsoft Store in its focus on trying to be the best experience for users hasn't always been the best experience for developers, but they've been refocused on developer experience the past few years, and the MSIX efforts really are interesting. Particularly because they've learned from the mistakes of earlier projects like ClickOnce. (I don't think a lot of people realize yet that MSIX already supports better-than-ClickOnce style application updating from file shares and web servers, bringing ClickOnce-style deployment essentially on par with Store deployment for MSIX.)
- danmaz74 7y agoMs for sure improved as of late. My critique was against the idea that they always were dev friendly.