>>My advice: Keep Visual FoxPro out of the CLR.
>
>Doug,
>
>To clarify my stand, my wish is that VFP.Net should compile to CLR thus getting WEB FORMS, ADO.NET, Crossplatform readiness, etc. but it should be backward compatible (Managed and Unmanaged Code) with its previous version.
>
>It's more on how I could participate in the Major League using one major tool? And that's what VS.Net promoters is talking about: "Choose the language of your expertise and you are comfortable with." The demise concern is just a by-product if I am not mistaken. All are just based on what I've heard, observed, and seen in the software devt arena. Sometimes better to do something and found it is wrong later than by doing nothing at all.

Jess;

I am not entirely sure where you are coming from. You think that VFP should be a part of the CLR while being backward compatible. That would require learning two versions of Visual FoxPro. What is wrong with learning how to use a .NET CLR compliant tool and the present version of VFP?

If your point is that you want to buy one product (VFP) I can understand your reasoning. Otherwise you have to buy two products (VFP and Visual Studio 7.0). Regardless of this you will still have to learn how to use two products or two versions of products.

Tom