>I disagree. Many learned net 3 yars ago and many are learning it now. The problem is that net is not a complete replacement for VFP yet.
>
>And I dare say it will be a long, long time, and maybe never. It's likely to remain a subset and a superset of VFP. I'm not referring to you, but those waiting for a "genetic match" are always going to be disappointed. It's better to learn the functional equivalents and functionally comparable features today, IMO.

Ignoring the possible future alternatives on the .NET platform. It is not all about VB.NET and C#. There are other developments going on, which might be a better fit in the long run. In the current event where the official news of the end of VFPs lifecycle is only one month old, it does not make a lot of sense to jump to hasty conlcusions.

I like, uh, love, uh, I'm addicted to, uh slaved to, highly (meta) data driven applications, and in the current state I'm not satisfied with either VB.NET or C#. I'm aware of all kinds of other alternatives that are complimentary in the .NET platform that just might be a solution to me, esspecially if you can use classes cross language. I'd like the .NET platform to mature and provide me with more options before I do ANY attempt on porting my HUGE codebase to any other platform. Its just a matter of economics.