"For now, I think it would be neat if the MS Fox Team could figure out a way to weasel in a single download page on the VFP Section of the MS Site where an all-in-one VFP runtime install could be started from..."

I Totally agree, it's just too stupid to ask a customer, or a developer for that matter, to go to a non-MSFT website to download the runtime files. MSFT should have a VFP runtime download page, with a subpage for each VFP version, each with their own subpage for the different language versions.

>I have always liked the thought of it. For now, I think it would be neat if the MS Fox Team could figure out a way to weasel in a single download page on the VFP Section of the MS Site where an all-in-one VFP runtime install could be started from... then give us a way to make our apps check if the runtimes are present on the system and offer to download and install them for the user if they're not. We could add some funky little flag setting in the config.fpw to initiate the check. Then we could bundle them if we wanted to streamline the runtimes that are installed, or just let our program do it through the internet. I know we could make our own and implement this through our own websites, but there's plenty of precedent for this sort of thing being offered by a company who's product you're developing in (mostly web-based right now though).
>
>>One of the biggest drawbacks to VFP is always distributing the runtimes. If this could be done with the OS in anyway, then developers only need to have to pass on the executable to the customer. It would make VFP apps much more portable. I don't see it ever happening though.
>>
>>
>>>>
>>>>Do you think there is any chance that the .NET team may agree to ship the VFP9 runtimes with the .NET framework? That would make it ubiquitous :)
>>>
>>>What VFP runtime has to do with .NET framework?