Heath Stewart

EXEs can also be distributed via WSUS, AD, etc. I wrote various extraction tools that took single- and multi-package chainers (Burn, or our previous chainers including those we've used since...

@stdin82 Windows Installer is shimmed specifically to return different versions even for those APIs. Windows closed those holes years ago. Any custom action DLL is loaded into `msiexec` and, thus,...

VersionNT 603 was the latest version any Windows Installer package will ever get, so I'm not sure what this proves. Version 6.3 was Windows 8.1. There's nothing higher. I've talked...

Admins and users alike generally hate reboots, though they are a fact of the way Windows puts files in use. Why would you want to force a reboot (even if...

A bit tangential, but *modifying* existing files during an install - whether MSI on Windows, brew, apt on debian flavors, etc. - is very problematic. Those "resources" can't really be...

Could this also include deprecation information a la nuget.org and npmjs.org (and related tools)? That is, a package in its entirety could be marked deprecated (with an optional array of...

Personally, I don't think it's worth cleaning them up. It's possible, but there's certain inherent risk and you'd need a custom action (at least within an MSI) to do it...or...

To note, Windows Installer is case-sensitive so the property must be `REMOVE=ALL`. That said, if you use the WixDependencyExtension and author your provide keys into the MSI, all the right...

@mjcavallari-zz it seems there's a discrepancy between what provider VSSetup has and what .NET is using, perhaps. Normally packages' dependencies would clean up just fine. I wonder if dependencies of...

I'll open an internal tracking bug because this may be caused by a difference in the VS package authoring given the changes in the SxS story from when the packages...