To be explicit, the problem is as stated: the Directory table in the MSI
file does not correctly link between directories and parent directories.
If the install works on some systems but not other, then look in the
Directory table for values that might not resolve correctly on some
machines. If it
Thanks Phil & Bob. I'll put the common Components in a Fragment and reference
them in both Packages.
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: July 5, 2013 17:40
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Should GUIDs be the same in two pac
I want to re-iterate what Blair said here.
The Burn engine does a whole lot of stuff to get your packages on the
machine correctly and get them off correctly. Caching the packages is a
very important part of that. If you don't register the Bundle as the ARP
entry there isn't anything to clean up t
1. Not currently, but it does sound like a good feature request.
2. Not directly using the default binder. The default binder normally looks in
the x86 directory of the directory the binder's assembly is running from for
the file named "burn.exe" (it's possible for it to look in a different platf
Without something like the bundle, the cached MSI is without its CABs ("Thank
You Windows Installer" for stripping the embedded cabs and for not storing the
external ones either) and thus Repair is broken unless the MSI is placed in
some protected area by its bootstrapper (which most don't do).
5 matches
Mail list logo
