The only way that kind of sharing will ever really work is if you use the same
component guids. If you are replacing a file from Product A and not using the
same component guid as A you've broken the rules, after which things get
unpredictable.
Permanent=yes is typically not a good solution, e
010 3:29 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall question
Try this
Run the command MSIEXEC /X
Notice the same message. No installer is involved. Message is coming
from MSIEXEC.EXE or other Windows components associated with it. Message
i
It's fixed after reinstalling. Thank you!
--
From: "Leung, John C.H."
Sent: Tuesday, May 11, 2010 3:12 PM
To:
Subject: [WiX-users] Uninstall question
> I understand that the uninstall information is store in registry key:
>
> HKEY_LOCAL_MACHINE\SO
Try this
Run the command MSIEXEC /X
Notice the same message. No installer is involved. Message is coming
from MSIEXEC.EXE or other Windows components associated with it. Message
is not coming from an installer. It's using a slightly different code
path depending on where you run it from (Command
David Scott wrote:
> I have an application that installs a website on a port which can be
> modified by the user at install time. The problem is that if they try
> to uninstall it from Add/Remove Programs I get an error because it
> tries to uninstall the website using the default port specified
rbok78 wrote:
> Therefore I decided to simulate that situation. I installed an add-in
> successfully. Then I only changed the registry value
> (HKLM\SOFTWARE\Microsoft\Office\11.0\Excel\InstallRoot\Path) to fictional
> path. I expected the add-in wouldn't be uninstalled due to different path.
> How
Sounds like you want a few RegistrySearch elements. After a quick search of
Gábor's tutorial I
found this if you want an example:
http://www.tramontana.co.hu/wix/lesson1.php#1.5
Rob
bob private wrote:
> Hi,
>
> I hope someone is going to be able to offer some advice on this issue as
> I seem
7 matches
Mail list logo