Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Vfp6r.reg
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Titre:
Divers
Thread ID:
00307852
Message ID:
00308265
Vues:
29
>Hi Ed,
>
>WISE Kind Of has VFP support built in. Is ships with a script (that you can modify if, for example you want to ship the MT-Runtime instead) that has all the VFP requirements in it.
>
>I've not used Installshield, but I don't see why it couldn't do much the same thing.
>
>OTH, I agree that if you're just doing an unattended install of the runtime then there doesn't seem much sense reinventing the wheel.
>
>I'm interested to hear what more stuff than what Wise handles without some intervention on the part of the programmer you do. I'm pretty pleased with WISE's ability to do almost anything I need (or could even contemplate needing. I certainly understand already know and own InstallShield Pro - the same applies to me and WISE. Perhaps this is installational inertia (-:
>

There are functions that I've needed where I've resorted to accessing Windows API calls and COM objects to get functions available from the operating system but not included as a part of the native "wizard mode" or standard install sequences - for example, self-restarting scripts where you know that a component may conditionally install, and if it does, must force a reboot in the middle of the install sequence. You want to autorestart the script - easy enough to do by writing a RunOnce key into the registry assuming you have the rights in the registry to create the key. I have a programming language available to me with IS Pro to add the functionality. At least one version of Wise I looked at had a similar but not identical scripting capability.

The key is, IS Pro gives me a language that lets me extend the functionality of an install in code. IS Express doesn't have that option. Wise has a scripting capability, but I'm not sure that all the Wise product line has it, and I don't know what things that I do that are not typical of an installation developer that are either better supported by Wise, or are scriptable without resorting to coding in another language and using some sort of interface scheme to get what I need. I'd suspect that many instances where i have to resort to using the scripting in IS Pro, I'd have to resort to scripting/programming for Wise as well. Since I know IS Pro already, and I know what has to be done if I need to resort to writing some C to add unique functionality to IS Pro, it doesn't make sense to go out and buy an equivalently expressive product for no real gain in productivity for me that would what full-blown Wise costs.

This is not a criticism of Wise in any way. It's a criticism of people who haven't bothered to figure out what's involved in installing an app in Windows and are clueless enough to believe they're smarter than the tools they're given to do the job in a minimally correct fashion. Buying IS Express, or Wise, or ANY capable install product, is not indicative of the idiot who believes, well, all I gotta do is copy some files into the Windows\System directory and I'm installed right. IT AIN'T THE CASE. You know it - that's why you bought Wise. I know it - I own InstallShield Pro and learned it a while ago. Mike Helland knew it, got IS Express, figured out what had to be added to its install wizard and got it working. But the person who just copies a few files without regard to OS/ version/existing app dependencies/desired install behaviors, on a good day remembers to run REGSVR32 against some of the .DLLs, doesn't bother to add the extra registry entries needed by the VFP runtime, has no idea what files are needed to make their freaking ActiveX controls work, and then bitches and moans because VFP doesn't come with a free tool that does everything for them is a menace to themselves, their customers, and to other developers whose stuff they're gonna bust. When they then point the finger and says "Bad, naughty VFP..." because they don't understand or give a rat's ass that they have no clue about the OS environment and figure they must be right because they copied the same files from their system directory under VFP, I really get pissed off. THEY BLEW IT, NOT VFP.

You can't do an adequate job as a developer if you don't have a clue about the platforms you run under and support. You don't have to be a systems weenie, sandworm or solder monkey. You DO have to learn the task at hand (installing an app) and if you aren't willing to learn to do it right, buy something that does it right for you, or pay someone who does know how to do it...



I need a drink...or three.

>Have a great festive season and all the best for the new year and beyond.
>
>Cheers,
>
>Andrew
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform