Hi All,
We're using setupbld.exe to chain two MSIs together (the first one say A.msi
spec'ed with -mu, the second B.msi with -mus). This works fine, except we're
testing the scenario where the user might try and run the setup.exe more than
once.
B.msi has some code to detect and prevent re-installations, but A.msi (which is
3rd party) does not. When I run A.msi by itself, it crashes with an error
message, so it seems that the combined .exe version is suppressing this. I
tried re-specing with -mus for A.msi as well in order to show any embedded UI
it might have, but again it fails silently. I tried turning on global MSI
logging via the registry
(HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\windows\Installer\Logging =
voicewarmupx!) but it doesn't show up there either...
Is there a way to debug this combined setup.exe (to confirm that this is in
fact what's causing the problem) or is this a known limitation?
Thanks,
Alec
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
