Greetings,
I faced a problem with patching a simple "Hello World"-style installation project: a single feature with a single component with a single file "file.txt". No registry entries, no shortcuts, no nothing.
The patch changes the "file.txt" file. If the patch is applied as
msiexec /p hotfix1.msp REINSTALL=ALL REINSTALLMODE=o
then the .msp-file doesn't get cached in %WinDir%\Installer and doesn't get registered in the Registry (::MsiEnumPatches() won't report nothing about the patch either). However, if applied with REINSTALLMODE=m, the .msp-file is cached and registered ok.
Same behavior with MsiExec 1.1 and MsiExec 2.0.
Question1: is there any sensible reason for this behavior? The "m" option relates to the Registry (which my application has nothing to do with), so why does it affect caching?
Question2: is this thing covered by any document? I've ploughed through the MSDN and the Internet and found nothing
Thanks a lot in advance,
Michael Steinhouse,
Software Engineer.
Novavox AG
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Patch applies ok, but doesn't get registered
Started by
mstone
, Oct 18 2002 14:30
2 replies to this topic