Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
InstallShield causing Big Headaches
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Installation et configuration
Divers
Thread ID:
00685737
Message ID:
00685962
Vues:
40
The big improvements in the $250 version of ISE are the ability to run Custom Actions from any point (not just the end of the install) and better support for updating software...
>Thanks. Initially we added the 'browse for database' feature to the app to solve this problem. However, I was concerned with current users upgrading to the latest version. They're all used to deleting the local database folder to use a shared one. Writing a note asking them to keep old folder will not work too well and I didn't want to add that problem to our support load.
>
>After spending a day on this problem I found a different solution. Instead of registering the database folder with ISE as a 'DATABAEDIR" I added the database folder as a regular folder and registered it as a new "feature". Now users can choose not to include this folder in their installtion. Even if they do, they can delete it safely without the installer popping up to reinstall it. It seems the installer does its auto re-install for files in the "Always Install" feature. I guess its thinking since its "Always Install" it should always be there!
>
>So you think the 'un-limited' edition of Express is better? From what I've seen its mostly adding billboards, text messages, and other useless stuff. The only feature that seemed useful is the dependencies scanner. I wonder if the full version still takes 10 minutes to build the installtion each time? Maybe the builder is smarter and stops when it encounters an error so you don't have to wait the full 10 minutes before you can correct the prolem!
>
>Our release was delayed 2 days thanks to InstallShield. I hope this is the extent of trouble caused by the new installer. We'll know next week for when our customers start using it.
>
>Mon
>
>
>>Solved in VFP, by having the user choose which data directory to use once the app is up and running. They can browse to find the directory, I check to see if it contains proper dbcs, and then it uses that. the value is stored in registry, among other private settings for the current user. The original data directory remains unused - wastes space, but doesn't hurt either.
>>
>>ISLE (note the LE - "Limited Edition") has lots of quirks, and I think it was just a way to get some burden off the VFP team's back. For one, they don't have to maintain an installer as they did in the previous three versions, and I remember that the old one had more problems than you mention. OTOH, some of the burden is thus passed onto our backs, but we're tough guys around here, we'll survive :)
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform