I've been using it with great success. There were only 3 troublesome things I ran across.

1) The VFP setupwizard knows which .dll's and other foxpro runtime files to include, and you have to add them in yourself with VI. However, you can create 'Merge Modules'...so all these files can be added at once each time you create a new project. Microsoft now has a VFP MergeModule you can download..but I'm sticking with my own becuase I like it better (it has some other stuff in it) and there's requires you to use 2 additional merge modules.
(If you want, I can send it to you)

2) No post-executiables. No way you can do this with VI. I just changed my app around a little bit so I didn't need one. There is a way you can do this with the Windows Installer, which is what the VI uses..but it's a major pain in the neck.

3) The shortcuts it creates: This is my bigest complaint. The VI lets you create sortcuts for your app (like on the desktop or startmenu)..but there is no way to change the 'Start-In' directory of them. This, to me..is one of the more stupid things I've seen in quite awhile. Anyway...I did find a way around that problem as well. On the Platform SDK CD there is this little program called ORCA that lets you edit the .msi file (what the VI creates). You can edit this 'start-in' thing there in 2 seconds.

I don't plan to use the VFP setupwizard again...I'm sticking with this.

>Hi,
> Anybody have any ideas/experience of using VS Installer to distribute VFP6 application? Please describe a bit...
>
>Thank you