According to the log file
[2013-08-12T17:22:27]i360: Creating a system restore point.
[2013-08-12T17:22:27]i362: System restore disabled, system restore point not
created.
the bootstrapper is already trying to create a system restore point. Does it
fail only because of some system settings, or co
That Windows Installer decides on "Feature level" which files to touch rather
than on "Component level" explains a lot, as I had used only a single
feature. After dividing this feature into >100 smaller features the patch is
ready after 18 minutes. That's still not great but a significant improveme
We have the following scenario:
- base installation with 14k files, 800MB msi file and about 1,4GB after
installation
- patch changing about 2k files and adding 13k files, 400MB msp file
- base installation took about 5-7 minutes to install
- patch took more than 40 minutes to apply (msiexe
Is it possible to get feedback from light (or any of the other WiX binaries)
what it is currently doing (e.g. "compressing file XY") or even something
like "37% finished?
(Verbose output is only a slight improvement as it stays rather long at
"Creating cabinet".)
--
View this message in contex
Identical file versions are definitely not the problem. (I just ran a test
with WiX 3.7 and it work just fine. Only got a warning that the patch
contains to files.)
It looks like your wixpdb files differ in more just the version number. Even
the referenced files are the same, the internal structur
5 matches
Mail list logo
