The MSI file is cached (without the files) because there's enough info
in there to see if repair is needed, such as file hashes, file version,
component info etc. Also a repair of a registry entry can happen
without going to the original source because that's still in the cached
MSI file.
The other behavior of repair is just the way it is. I'd like to see an
option in MSI to cache the actual MSI file (when it does really contain
the cabbed files).
Phil Wilson
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Albert van
Peppen
Sent: Tuesday, September 11, 2007 12:47 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Repair issue
Thanks for your quick reply :)
This makes you wonder why the MSI file is being cached anyway...
Is this a general issue (e.g. is it still there in WiX 3.0 or in MSI 4.x
?) and is there a way to get around this?
The most likely way is to copy the MSI file onto a directory after
installing and then altering the registry accordingly (as is noted in
Rule 31)
But i don't think this a nice solution.
Regards,
Albert van Peppen
________________________________
Van: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Namens Wilson, Phil
Verzonden: maandag 10 september 2007 23:15
Aan: wix-users@lists.sourceforge.net
Onderwerp: Re: [WiX-users] Repair issue
If the product requires a repair to re-install a file then it will want
the original MSI file, and the best approach to this issue is to have
the original MSI available. You can't really guarantee that a repair
will never occur. Unpacking a setup and installing the MSI from a temp
location that gets deleted is not a good idea.
Tao of the Windows Installer, Rule 31
http://blogs.msdn.com/windows_installer_team/archive/2006/05/24/605835.a
spx
Phil Wilson
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Albert van
Peppen
Sent: Monday, September 10, 2007 8:43 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Repair issue
Hi,
Does anyone know how the debug problems with the ARP repair
functionality?
The problem in my case is that the repair gives a 1706 error; (Dutch
version sorry ;)
Fout 1706. Kan geen installatiepakket vinden voor product Drumis -
Databaseonderdelen V2.90.2352.0. Voer de installatie opnieuw uit met een
geldig exemplaar van het installatiepakket DatabaseSetup.release-3.msi.
MSI (s) (30:60) [15:52:35:015]: Product: Drumis - Databaseonderdelen
V2.90.2352.0 -- Fout 1706. Kan geen installatiepakket vinden voor
product Drumis - Databaseonderdelen V2.90.2352.0. Voer de installatie
opnieuw uit met een geldig exemplaar van het installatiepakket
DatabaseSetup.release-3.msi.
What basically fails it that the installer attempts to read the source
MSI file from the original installation source (which might be a CD or a
temp-folder). Anyway, after installation the MSI file is no longer
available.
In the WINNT\Installer cache is a copy of the msi file. This matches the
one found in the registry at;
HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\Userdata\S-1-5-
18\Products\<some id>\InstallProperties\LocalPackage
Am i doing wrong? Or is there something that is required in the WiX
file?
I am using WiX 2.0.5325.0, tested on Windows XP, SP 2.
I have my own CA DLL embedded in the MSI file.
Regards,
Albert van Peppen
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
