Your previous install was per user, the new install is per machine, and one
will not upgrade the other. The Windows default if unspecified is per user,
so perhaps if you never set it in the original install it defaulted to per
user.
The question is: Why has the new one a different setting? I
I finally found the solution (by trialerror):
Its the VC CRT merge module I added. It requires per-machine install and
thus whole install scope changes.
Any ideas how to solve that (if possible with keeping installer per-user)?
--
View this message in context:
Has nobody an idea what (and why) is going wrong?
As far as I can see, it doesn't find the old installation because of
conflicting InstallScope. But I have no idea, why install scope is different
(even if I explicitly set it).
--
View this message in context:
files that were not already in
1.56 are removed.
For previous versions, updating worked (e.g. 1.55 - 1.56).
You can find modified project here:
http://kloke-witten.dyndns.org/~philipp/Temp/win_installer.zip
Any ideas?
PKEuS
--
View this message in context:
http://windows-installer-xml-wix
/~philipp/Temp/win_installer.zip
Any ideas?
PKEuS
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Major-upgrade-stops-working-after-doing-small-changes-and-switching-to-3-6-tp7581475.html
Sent from the wix-users mailing list archive at Nabble.com
You can find verbose log file here:
http://kloke-witten.dyndns.org/~philipp/Temp/msi_log.zip
There are some lines about finding related products, where it says
FindRelatedProducts: current install is per-machine. Related install for
product '{1CC8C271-A877-4DF0-B1DE-C1B7D83521BC}' is per-user.
6 matches
Mail list logo
