Hello Igor,
is there any chance that you could provide us the source code?
Bets regards,
Christian
-Ursprüngliche Nachricht-
Von: Igor Brejc [mailto:igor.br...@gmail.com]
Gesendet: Samstag, 20. Oktober 2012 20:04
An: General discussion for Windows Installer XML toolset.
Betreff: Re: [
- Forwarded Message -
From: jpalmer1...@comcast.net
To: wix-users@lists.sourceforge.net
Sent: Saturday, October 20, 2012 7:38:53 PM
Subject: Define as x64
I have a windows service that needs to be installed on a 64 bit server. Can
someone point me to the documentation or tutoria
and adding some detail about "did not work" would help. Maybe you saw
an msiexec message box showing the correct syntax because yours was
incorrect, or maybe it started and failed in some way.
Phil W
-Original Message-
From: Rob Hamflett [mailto:rob_hamfl...@sn.scee.net]
Sent: Fri
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. A verbose MSI log of the install of the original could be useful -
See the docs for ComponentId here:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa368007(v=vs.85).as
px
It's allowed. It just means it won't be managed by Windows, meaning amongst
other things that you'll need to remove it yourself.
Phil W
-Original Message-
From: Uma Hara
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:
http://windows-installer-xml-wix-t
6 matches
Mail list logo
