Hi Rick,

Do you actually use VSI? I tried it a bit over a year ago and found it so limiting that it was useless for all but the simplest installs. You can't manage patches, and it doesn't offer anything in the way of dialog management either. I dumped the whole thing and went to IS Developer 7 (now 8). For simple installs I use Jordon Russel's Inno Setup, which is a free (not shareware) product from www.jrsoftware.org. Inno is really a great product.

IS Developer is OK. The problem with IS has more to do I think with the Windows Installer (msi) technology itself which is long on promise and short on delivery. When you run into MSI issues they seem to be nightmares. The old scripting technology was (IMO) much better. I've got script-based installs that have worked for years. MSI installs often require the original install files (usually the CD) when you get in trouble.

And you're right; IS Express is one BIG advertisement.

Rich


>>I'll forward your issues to the appropriate folks, however, IS is not an MS product so what I can do is limited.
>
>
>Why is it that we're using INstallshield anyway in VFP? Couldn't this have been rigged so that we use the Visual Studio Installer Projects instead? All that needs to happen for this is that the Fox team provides the merge modules and the rest is taken care of automatically. I suppose we can do that now already.
>
>VS installer is not perfect either but the IS path is just one big advertisement for IS...
>
>+++ Rick ---