I am running an installed EXE during the uninstall. This EXE requires DLLs that
were also installed. But the EXE is not running. From the log I can see the
custom action is scheduled, some DLLs are removed, then it starts running. The
EXE will not run without those DLL. The EXE uninstalls a d
NOT
Installed
Installed
Any idea how I can get this to work?
Kurt Jensen
Senior Software Engineer
Ophir-Spiricon LLC
kurt.jen...@us.ophiropt.com
www.ophiropt.com/photonics
The True Measurement of Laser Performan
some additional conditions to ensure that it only runs when
the product is being removed, such as REMOVE~="ALL".
-Original Message-----
From: kurt.jen...@us.ophiropt.com [mailto:kurt.jen...@us.ophiropt.com]
Sent: Tuesday, June 11, 2013 7:10 AM
To: wix-users@lists.sourceforge.net
Sub
ituations where you don't want it to be
called. If you do a repair, add or remove features, then your remove will be
called because the Installed condition is met.
Phil
-----Original Message-
From: kurt.jen...@us.ophiropt.com [mailto:kurt.jen...@us.ophiropt.com]
Sent: Thursday, June
We use a third party MSI which requires a command line parameter. Despite
repeated searches I cannot find out how this can be done.
The actual command we are trying to duplicate is 'msiexec /i "pylon 4 Runtime
x64 (GEV) 4.1.0.3660.msi" ADDLOCAL=FilterDriver,PerformanceDriver'
We tried but we g
Never mind... I copied wrong from the documentation wrong. There is an 'x' in
front of each 64...
Thanks for listening :)
-Original Message-
From: Jensen, Kurt
Sent: Monday, May 05, 2014 2:15 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] MsiPackage command line parameter
Have a new installation that refuses to upgrade. On each new release the
installer complains. That "Another version of this product is already
installed... Below is the Product.wxs file. Build and install this version,
change BGProductVersion to 1.11.5241.1234, build and install, "Another
ve
a major upgrade, ditch the upgrade elements for a
MajorUpgrade one, change the product Id to *.
Be aware that the MSI only pays attention to the first three parts of the
product version, but in this example it should upgrade.
-Original Message-
From: kurt.jen...@us.ophiropt.com
Working on release of an upgrade. If I install no prior version installed then
everything works fine. If I upgrade from a previous version then about 25
files are not copied to the installation directory. In the log the missing
files seem to be listed normally except for the FileCopy operation
Continuing
Development Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original Message-
From: kurt.jen...@us.ophiropt.com [mailto:kurt.jen...@us.ophiropt.com]
Sent: Tuesday, February 3, 2015 9:51 AM
To: wix-users@lists.sourceforge.net
Subject: [W
1) Our MSI sometimes requires a reboot after certain upgrades. We have
programmed ScheduleReboot with the necessary condition. The previous version
is removed and reboot is requested when run directly from the MSI.
a) No reboot is requested when run from the encompassing bundle. The MSI log
s
Think we found the real problem
[2D80:2FB8][2015-04-02T12:28:40]i103: Detected related package:
{DCB7DC05-888D-4B9B-904B-EA1DB739C994}, scope: PerMachine, version: 6.4.0.171,
language: 1033 operation: Downgrade
[2D80:2FB8][2015-04-02T12:28:40]i103: Detected related package:
{DCB7DC05-888D-4B9B-
Now we KNOW we have found the -real- problem... :)~
Tried to use Upgrade to detect when a reboot is required:
The last part caused the double detection by the bootstrapper and caused the
installation to be skipped.
How then do we get the version that is being
13 matches
Mail list logo
