>>I see this as a growing need, for one reason: ActiveX controls will no longer be developed, or at least not as much, as .NET takes hold. So, if we want to be able to have the latest in controls, we'll have to be able to run the .NET versions.
>
>Which also means having to distribute the .NET (runtime) framework with your VFP apps ... which is weighing in at over 30MB these days.

Yes you are correct - however disk space these days is cheap, and seeing how everyone else is going to be using the .NET runtimes the users are going to need it anyway.