Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Detecting and overwriting
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Installation et configuration
Divers
Thread ID:
00569164
Message ID:
00572814
Vues:
17
This message has been marked as a message which has helped to the initial question of the thread.
>Hi Mike,
>
>Thanks for your feedback. I'm familar with InstallShield and building *initial* installations. However, what I'm looking for is a way for our software to:
>
>a. Recognize conditions where dependent files like ActiveX, DLL, Fox runtimes, etc. need to be updated based on a downloaded list of files and version numbers
>
>b. Detect and proactively attempt to correct situations where expected (dependent) files like ActiveX, DLL, Fox runtimes, etc. have been accidentally deleted or corrupted (optional corruption detected by comparing checksums)
>
>In other words, I'm not looking for a way to initially install our software - I'm looking for a way for our software (once its already been installed) to proactively verify its environment and attempt to correct any missing, out-of-date or corrupted files upon which our application is dependent.
>
>Does this make sense? (Am I being toooooo paranoid?!)
>
>Thanks!
>Malcolm

I don't think it's too paranoid to want to make sure your software will work correctly. I think that Windows Installer can address most of your concerns, though, because it can be used for upgrades, updates, and patches, not just initial installations.

a. You should be able to handle ActiveX, DLL, & runtime file updates with a patch. A patch updates all components of an existing installation to their new versions.

b. WI gives you the ability to repair an existing installation by going to Control Panel, Add/Remove Programs. If you suspect a problem, you can manually run the WI repair option to restore all the components of the installation to their latest version. I thought that WI was also capable of detecting and repairing out-dated or corrupted components automatically, but I'm not sure about that, nor do I know how that behavior is triggered. I haven't taken the time to do any testing in that area.

Anyway, the bottom line is that you can download the Windows Installer SDK from Microsoft's web site for free. I recommend that you look through the help file(s) to decide for yourself if it might accomplish what you want.

Good Luck!
Mike Potjer
Optimal Solutions, Inc.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform