3 ms·
I have to agree with others here. It's better to use Wix as a thin layer on top of Windows Installer but the documentation is very, very poor. I spent a week o
by micovec 3y ago
I have to agree with others here. It's better to use Wix as a thin layer on top of Windows Installer but the documentation is very, very poor.
I spent a week of trial and error to create an installer just to find out that I had several installations of my app because of some misconfigured xml document from testing. A nightmare to uninstall to say the least.
I highly recommend to test your installers inside a VM or you'll screw up your system.
Also good luck if you want custom behaviour from the installer. The documentation for that is far worse than it is for the standard msi installer.
- jasonjayr 3y agoI recently learned about the "Windows Sandbox" https://learn.microsoft.com/en-us/windows/security/application-security/application-isolation/windows-sandbox/windows-sandbox-overview https://learn.microsoft.com/en-us/windows/security/applicati... Perfect for testing things that might screw up a Windows system in a 'clean' environment.
- micovec 3y agoThis is very handy! Especially for installers. Thanks, I'll write it to my list of handy tools.
- Kwpolska 3y agoSandbox is great in general, but it might not work for working with something deeply integrated into Windows (I remember some installer failing because a Microsoft thing wouldn’t install). > Pristine: Every time Windows Sandbox runs, it's as clean as a brand-new installation of Windows. I can see my custom fonts in the Sandbox. Which makes me wonder, what else is not actually pristine about it?