Hi Costas,

>1) Why doesn't VFP support .NET?
I think this is because the product would have had to be rewritten from scratch and also because in order to integrate like the tools from vstudio with .net, some of vfp's native functionality would be lost.

People often make the mistake of placing vfp in the same category as the other tools in vstudio (vb, vc, vj), however, vfp is not JUST a programming language like the others; it's rather an integrated development tool which requires absolutely NO third-party components to create a completely stand-alone application.

>2) Will VFP7.xxx support .NET and if not, why not?
VFP 7 has been released already. Any .xxx release would be in the form of a service pack, which means that the present architecture will remain unchanged.

>3) Will VFP8 support .NET and if not why not?
I have no idea.

Hope this helps!

Alex