>Hi Doug,
>
>Would it break the VFP9 license if someone created a fully up to date package to install all updates to the VFP9 development environment, along with all released auxiliary and optional files, such as GDIPlus.dll, XSource, Sedna etc etc plus their related hotfixes and such?
>
>The purpose would be that you could reinstall the VFP9 RTM, and by running this package know that you have not missed anything or created any conflicts between file versions. A side benefit would be that all VFP9 developers who used such an updater would have a common platform.
>
>I believe that ftp.prolib.de has created something similar to this for VFP9 runtime files and of course it would be important that there were no conflicts between their runtime installer and the suggested updater to the development environment.
>
>This would be a meaningful project for VFPx.
>
>Alex

Alex

If that someone created the package for him/her self and did not distribute it there should be no problem.

The files from prolib.de are the runtimes which you are allowed to distribute anyway.

But VFP itself, the IDE and the support and tools/ applications cannot be distributed.

So I think your idea is great but what can be posted on VFPX would have to be some sort of batch script that collected all these files and processed them.

An idea would be to use some tracking software and do a clean VFP install into a virtual machine and then use the report of the tracker to generate a list of files added/changed and registry entries etc. Then base your script on this.

This is basically how creating Virtual apps work.