Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Problem Including VFP 9 runtime library merge module
Message
General information
Forum:
Visual FoxPro
Category:
InstallShield
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Vista
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01266597
Message ID:
01266873
Views:
11
>Hi Michael.
>
>>If this advice was coming from someone other than Doug Henning I’d probably continue working with Installshield for as long as it took. I can't believe all the time and money I’ve spent on Installshield. Economically speaking, it’s just a sunk cost. I’ll get started with Inno Setup right away. I can’t afford to lose any more time. Thanks Doug!
>
>Thanks for the kind words. I agree: the time and money you've spent in the past is sunk (my business partner the accountant taught me that). I was in exactly the same straits about four years ago: InstallShield was giving me grief, I had customers to satisfy NOW, and couldn't afford to waste any more time trying to figure out why it was misbehaving. Right around that time, an issue of FoxTalk with Rick's first Inno article arrived. I gave it a shot and in literally two hours had completely replaced my InstallShield setups with Inno, and haven't looked back since.
>
>Doug

Well, I'm inspired, too. All my apps are custom and run from the network so I just install the app manually the first time and have an InstallShield setup for only the runtimes. But I do have one app that goes out to about 10,000 dealers for one of my clients. I've been thinking about using Inno, but once I got the InstallShield setup done, it just needed a little tweaking each year (program is updated yearly). The disks just went out and it appears there are more issues this year than in years past. Perhaps it's time for a change . . .
eCost.com continues to rip people off
Check their rating at ResellerRatings.com
Previous
Reply
Map
View

Click here to load this message in the networking platform