dbareis

You need to log the installs and see what happens. It seems likely to
me you didn't install the first version of "one.msi" before instaklling
the second

Bye,
Dennis Bareis

rucha

Hi,

Thanks for the quick reply...but I didn't get what you are trying to say...
Even logging hsn't helped...
Probably I have framed the question in wrong manner...(the level of
directory where we are installing file doen't make any difference..)

Let's start it over again...

I have embedded the directory structure Main (where I want to install files
in, at the target location) in Directory table...
I have custom action DLL which sets the TARGETDIR to C:\ at
install/uninstall time...
(I have specified no condition for it's execution...)..
assume 'Main' is already present in C:\
I have one custom action for Backup/Restore if file to be installed is
already present at target location...
Now,
I have one msi 'a.msi' which installs file 'a.txt' in 'Main' Dir ...
If I install and uninstall 'a.msi'...it works as expected and 'a.txt' is
removed...

I have one msi 'b.msi' which installs two files 'a.txt' and 'b.txt' both in
'Main' Dir...

1) if my 'a.msi' is not installed then install/uninstall of 'b.msi' works
fine...i.e
both 'a.txt' and 'b.txt' are removed...

2) If my 'a.msi' is already installed and we install 'b.msi' then 'a.txt' is
already there
at target location hence it is backed up( by my custom action ) and gets
replaced
with the new 'a.txt'...'b.txt' directly gets installed without any
backup...
Now if I uninstall 'b.msi' the original 'a.txt' is restored back (by my
custom action
dll) but 'b.txt' remains there as it is...ideally it should get
uninstalled....and still I
don't get any error message...
Now if I uninstall 'a.msi', 'a.txt' is removed completely...but my
'b.txt' remains
untouched(obviously...since 'a.msi' hasn't installed it !)

Logging hasn't helped ...since it reports that all the processes have
returned success and thus install/uninstall has been successful in any case...

What I have gathered from all the trials and errors I did was that ,
1) If the msi is the only msi installed there...it works right.
2) When a msi is already installed and another msi is created to replace
files
already present at the target location everything works fine...but if
new files are
installed...those new files don't get uninstalled...

I hope I have been able to forward my question correctly...
Plese...Help is needed...

Thanks,
Rucha

rucha

Adding to the question...I have realised that this problem wasn't occuring
when I had hard coded the value for 'TARGETDIR' in the Property table....


facing this problem...
I tried changing the conditions for that custom action in
InstallExecuteSequence...
tried,
1)specifying no condition so that it is executed during install/uninstall..
2)specifying REMOVE<>"ALL" ...so that its executed at all times except
during uninstall...

It will be great if someone helps... "Rucha" wrote:

dbareis

Hi,

Have you tried also sequencing in "InstallUISequence" or are you only
testing silent installs?

Also from what I've seen Windows Installer will remember the values of

Bye,
Dennis Bareis

rucha

Thanks so much...
Actually it was my mistake...
This problem occured because the component id's were same for both the .msi's
so it didn't uninstall properly..

Thanks,
Rucha