How do I detect uninstall or minor upgrade or first time install. I looked at
the values in the table in the following article
http://stackoverflow.com/questions/320921/how-to-add-a-wix-custom-action-that-happens-only-on-uninstall-via-msi
and I don't think they are correct! Are they? Why do I
If you download an msi file and choose to run the file (rather than save it),
Internet Explorer will add a number to the filename in brackets (such as[1] or
[2] etc...). Windows Installer saves this filename in the registry and expects
the same filename if you run an upgrade/repair or
If you download an msi file and choose to run the file (rather than save it),
Internet Explorer will add a number to the filename in brackets (such as[1] or
[2] etc...). Windows Installer saves this filename in the registry and expects
the same filename if you run an upgrade/repair or
Using the following command 'msiexec /i SampleUpgrade.msi REINSTALL=ALL
REINSTALLMODE=vomus' for minor upgrade causes the following rule not to be
obeyed
Feature Id='Service' Level='1'
ComponentRef Id=Monitor /
Condition Level=0FILEEXISTS/Condition
/Feature
Is there any way I can do
1. Is there any difference between installing managed windows services versus
unmanaged ones using standard custom actions?
2. If yes then what is the best way to install unmanaged windows service (any
examples?)
I just wanted to get some feedback from you guys to save some time since I am
not
or read a really good thread that deserves
attention? E-Mail Me
- Original Message
From: Mark Turek turekm...@hotmail.com
To: wix-users@lists.sourceforge.net
Sent: Sat, February 12, 2011 5:01:52 PM
Subject: [WiX-users] Unmanaged c++ window service installation
1. Is there any difference
How do I control the sequence of InstallValidate action. I want my custom
action to execute before InstallValidate displays filesInuse dialog. So far I
played couple of different tricks with the sequence attribute but it does not
seem to have any effect.
I have a requirement where installation needs to proceed even if the exe
(actually any installable component) is running and loaded in the memory. The
installation should be silent and whenever currently running executable is
closed the next startup should proceed with the newly installed one.
copy and runs that.
Of course you still need a core launcher app to deal with, but overall I
find this works reasonably well.
Andreas Mertens
NVision Ideas Inc.
- Original Message -
From: Mark Turek turekm...@hotmail.com
Date: Friday, February 4, 2011 1:28 pm
Subject: [WiX-users] bypass
9 matches
Mail list logo