>>> It was very recently that Steve Ballmer said that small/medium business is MS' biggest market segment. As that sinks in at MS there may still be hope to see the CLR changed to support things like .DBFs and to have a VFP server and such. Or there may be other ways to bring VFP into the .NET fold. After all, MS makes these rules up and has the power to do whatever it wants. <<
>
>#1, that hasn't happened and probably won't happen. #2, we as VFP developers don't want it to happen. As George explains better than I could, .NET-ifying VFP would be its death knell. It would lose everything that makes it unique. It would be no more than a watered-down VB.

We're all VFP developers here, and I don't see every last one of us agreeing with #2. Yes George explains why he believes VFP.Net will be the end and it makes sense, but it's a matter of opinion and perspectives.

Again, I'm not so sure we need to lose everything that makes VFP unique. Furthermore, what makes VFP unique will be different things to different people.

The argument of a feature-skimmed VFP resembling a watered-down VB does not explain VB.Net. After all, what is VB.Net if not a watered-down C#? The multi-language platform promise of the .Net framework is one of its stronger offerings IMO.