> One more question though: in this day and age where space > is cheap, is there a good reason NOT to put the runtimes in > the App's folder directly? That's how I've set up my Inno > scripts for years.
I don't see any reason not to do it that way. In fact, I'm starting to lean towards doing it that way myself, mostly so that a VFP9 SP2 app can co-exist with a VFP9 SP1 app on the same machine without one of them overwriting the other one's runtime files in the common location. Using Inno Setup or another non-Windows Installer setup tool, you can easily place the runtime files in the app's folder. However, when using InstallShield or another Windows Installer-based setup tool, you're probably deploying the VFP9 runtime files via the Windows Installer merge module, in which case you don't have any control over where the files are written unless you hack the merge module. FWIW, I use Inno Setup for all my deployments except in cases where the client requires a Windows Installer setup, in which case I use InstallShield 2009 Express edition. _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
