Hi,
I am new to MSI and I am evaluating InstallShield 8 (may be 9) and MSI as our new method of installation.
I am trying to research some areas of concern and among them auto-repair.
I could not find any clear description under what conditions the auto-repair kicks in.
I looks like from what I found the auto-repair happens only if the operating system needs to load key executable or DLL and it is missing.
I did the following test: I have a shortcut S1, that envokes executable E1 that in turn executes executable E2. Executable E2 has a satellite DLL D2. E2 can be looked at as a interpretator. So it has some other file R1 that is a compiled (from some language) program that E2 knows how to execute.
S1, E1, D1, E2, R1 are installed using MSI basic project with InstallShield default values
E1 - component and key file
E2 & D2 - component and E2 is key file (I know that they better be different components but this is out of scope...)
R1 - is a key file in the component that contains this and other R-style files. The R1 is the first R file the E2 supposed to execute when started.
In the following tests I always started the chain by clicking the shortcut.
Here are the results:
Action | Expected | Actual
Deleted E1 | E1 repaired | E1 repaired
Deleted E2 | E2 repaired | E2 repaired
Manually corrupt E2 | E2 repaired | NOT repaired
Manually drop in diff ver of E2 & D2 | E2 & D2 repaired | NOT repaired
Delete R1 | R1 - repaired | NOT repaired
At that point I gave up and started looking for more information on the subject but could not find any...
Help!!!
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.
MSI Auto-repair
Started by
secam
, Oct 16 2003 22:08
1 reply to this topic
JohnAlt2
-
- Members
- 6 posts
Posted 30 October 2003 - 12:44
Are all the components sitting in the same feature? If not what is the component/feature arrangement.
Corrupting files: Define, in what way are they corrupted, has the file size changed?
Replacing files: Are you replacing with a newer or an older version of these files?
Windows Installer can check:-
Whether files exist and is readable
Whether they are of a different version (verioned files only)
If the have the same Hash value (if there's an entry in the MsiHashFile table)
Windows installer does not do a byte level comparison of files to detect corruptions.
Corrupting files: Define, in what way are they corrupted, has the file size changed?
Replacing files: Are you replacing with a newer or an older version of these files?
Windows Installer can check:-
Whether files exist and is readable
Whether they are of a different version (verioned files only)
If the have the same Hash value (if there's an entry in the MsiHashFile table)
Windows installer does not do a byte level comparison of files to detect corruptions.
