>I am trying to impress clients with what seems to be a positive comeback for VFP. I have sent the Balmer video, the VFP article in MSDN and so on. However I need to know how to answer the questions:
>
>1) Why doesn't VFP support .NET?

.Net is NOT a product. Do not confuse .Net with Visual Studio .Net.

VFP does support .Net. VFP fully creates and consumes web services. It does not participate in the CLR because there wasn't a demand for it. If it did participate in the CLR, what would there be to differentiate it from VB?

A question to ask them is, what gains would there be for VFP to support the CLR? What would you have to lose in VFP?

Also, VS .Net is a version 1.0 product and it is possible that it will have the same problems as other version 1.0 products.

>
>2) Will VFP7.xxx support .NET and if not, why not?

See above.

You won't see VFP7 support the CLR because it would require some major changes to the product.

>
>3) Will VFP8 support .NET and if not why not?

Microsoft has not announced that it will. Microsoft has not announced that it won't either.

>
>I think know why VFP7 does not support .NET (did not want to delay the product). Will there be a 7.xxx product that does?
>
>Thanks