>I would have thought that including the runtime libraries in the Install Shield build would have included >all< necessary runtime files. Short of telepathy (and folks like you!) what's a harried developer to do?

*sigh* And to think of all those hours I spent writing the deployment whitepaper that can be found on the VFP7 CD and can also be found here.

> For the majority of things I do, it's too complicated and quite cumbersome.

Sounds like someone needs a demo. I managed to run through creating an install package in about 5 minutes during the Orlando DevCon keynote. IMO, InstallShield is easier to learn than the setup wizard was. For instance, how many times has the question been asked about how to get your app into the start menu? Yeah, that was intuitive. :-)

> I particularly disliked the handlling of destination directories (would
> anyone really install a DLL in "c:\program files\your company name\default"?)

Yup. DLLs don't go in \system32 anymore.

> and of the registry (I don't really want to mess with registry keys: just >register the file properly as 6.0 used to do.)

So don't mess with the registry. Just because the option is there, it doesn't mean you have to use it. The merge modules for the VFP runtimes assure that those files get properly registered.

>OK, I'm through whining, but I'd pay $$ to get the Setup Wizard back.

You'd pay money for a 16-bit app that doesn't look nearly as professional, and doesn't conform to Windows logo requirements?

Mike Stewart