4 replies to this topic

[slescure]

Hi,

I am using the REINSTALL option as a command line of my product installation. My problem is that it seems that for Merge Modules and registry entries, the INSTALLDIR value is not correct...

Example :
I install my application to D:\MyApp (The default being C:\MyApp for instance)

Then I upgrade by launching a new setup.exe with new features :
- All files are correctly copied to D:\MyApp
- The registry value that I defined as [INSTALLDIR]\Foo, and that was correctly written the first time to read "D:\MyApp\Foo" is updated to "C:\MyApp\Foo"... ???
- A merge module that I chose to install to INSTALLDIR is updated by being installed to C:\MyApp instead of D:\MyApp

Any help?
Thanks,
Sébastien

[Balachandar]

Hi ,
Check for Detination of ISMergeModule table. Make sure it is [INSTALLDIR]

Cheers.

[slescure]

Hi,

Yes, the destination of my merge module in the table is [INSTALLDIR]... Unfortunately... :-( Actually, the merge module installation runs fine at the correct location the first time I process the installation. The location problem occurs only if I make an upgrade.

Thanks for the try anyway...
Sebastien

[Glytzhkof]

What value do you assign to REINSTALL for this installation?

[slescure]

REINSTALL=ALL
REINSTALLMODE=voums