After some more research .. I got my answer.
-Original Message-
From: Robert Hermann [mailto:rob.herm...@nicewareintl.com]
Sent: Tuesday, August 16, 2011 3:15 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] System wide Environment variables and t
I've done some research in using system wide environment variables (not wix
installer session variable) and the exit dialog. I've been able to setup an
environment variable and then run the installer and echo the value of the
variable in the Exit Dialog screen.
I take it one step further and o
I am using WixDifxAppExtension to install a printer driver as part of an
application installer. The WiX source is as follows:
The corresponding custom actions apparently complete successfully. However, the
install log file includes the lines:
Had same problem with any signed msi. In my case defect reproduced ONLY on
2008 SP2 (x32 and x64). Tested on 2003 and 2008 R2 - worked fine.
Workaround was found accidently: import certificate of publisher, the msi was
sign which's key.
Import certificate:
1) go to file (msi in my case) property
2)
Hey.
In implementing my own bootstrapper application, I've implemented the
DetectRelatedMsiPackage event to be informed of MajorUpgrades if an msi with a
lower version number is installed, and this works fine. However, the
RelatedOperation enum also contains a value called Downgrade, but when I
Yes it's possible, see http://msdn.microsoft.com/en-us/library/aa368010.aspx &
http://msdn.microsoft.com/en-us/library/bb204770.aspx#concurrent_installs but
you shouldn't do it for the reasons listed on those pages.
Use a bootstrapper to sequence your pre-requisites. WiX v3.6 ships with Burn or
6 matches
Mail list logo
