Thank you for your ideas. I will fiddle with Mike's solution and see if I can
get things going as I would like.
The more I read about my scenario, the more I realize it is probably best to
not be overwriting a user-edited file, in fact. So perhaps I am going down the
wrong road.
Cheers.
--
s] Replace component on reinstall
You could try specifying a version on the File element. I think that will
cause Windows Installer
to always replace the unversioned file on disk with what it thinks is a
versioned file.
Rob
On 17/08/2011 16:30, The Eligible Bachelors wrote:
> Hello,
>
> I w
Hello,
I would like to have a component that does not get removed at uninstall.
However, if I uninstall and install again, I would like the file to be replaced
with the one in the installer. Here is my code:
The problem is when I install and uninstall,
uninstall
Look at a verbose log file. It will show you the action states of the
Components.
On Wed, Mar 16, 2011 at 6:53 AM, The Eligible Bachelors <
theeligiblebachel...@yahoo.com> wrote:
> I am having trouble figuring out why a component is not being removed at
> uninstall time. This pro
.
Cc:
Sent: Saturday, March 19, 2011 2:01 PM
Subject: Re: [WiX-users] Component is not getting removed at uninstall
Look at a verbose log file. It will show you the action states of the
Components.
On Wed, Mar 16, 2011 at 6:53 AM, The Eligible Bachelors <
theeligiblebachel...@yahoo.com>
> Action="write"
>
>
> Key="Software\Classes\extfile\shell\open\command"
>
> Value ='"[#MainEXE] "%1"'
>
> Type="expandable"
> />
>
&
Setting it to TargetFile='MainEXE' gives me the same ICE69 error.
If I set it to TargetProperty='MainEXE' the install log shows:
MSI (s) (64:68) [11:20:53:948]: Executing op: RegAddValue(,Value="" "%1",)
WriteRegistryValues: Key: \Software\Classes\extfile\shell\open\command, Name: ,
Value: "" "
Ok. So I have removed the property with the file search. Now it looks like:
...
...
Produces
"Unresolved reference to 'File:[MainEXE]' in section ...
If I then change it to TargetFile='[#MainEXE]', I get the same error.
If I change it to T
I am having trouble figuring out why a component is not being removed at
uninstall time. This problem happens when the MSI is run in Windows 7. When run
in XP, the component is getting removed as expected.
The Wix file is somewhat complex and contains a REINSTALLMODE property.
What I have done
Great. I added Execute="deferred" and Impersonate="no" to my custom actions and
it seemed to fix the problem.
I certainly dont want to go against UAC. I want to do what is right, whatever
that may be, so thanks for the help.
> You need Execute="deferred" custom actions with
> Impersonate="no".
This is mostly a MSI question and not too WiX specific.
I am porting an old WiX (3.0) installer from XP to Windows 7. The installer
needs to be run as an admin because makes several calls to external programs
that need admin privileges (to register COM objects and such).
Even when I am logged i
Thanks for the input. Yes this is a single MSI with 3 features.
I have tried the [#executable] idea, but I get an ICE69 error (MAINEXEC
references invalid file).
First of all what is the best resource for getting help with advanced WiX
topics? A book or mailing list will do. I have been mostly using stackoverflow.
And now for my question. I have an installer with features A, B (optional) and
C (optional).
Feature A is an executable and B and C are DLLs
13 matches
Mail list logo
