Fortunately, VFP does not live on the .Net path. Whether the two are parallel/mutually exclusive paths I don't know. The future will bear that out. In the near term (12-18 months), .Net is going to have zero impact on the VFP world.

Why?

The programming models are completely different. For one thing, VFP has a delivered application base!!!

Okay, that was a cheap shot...

Seriously... .Net is intriguing, but it is going to take a while to mature. The key question I have is whether MS will ultimately let .Net mature. As far as I am concerned, MS pulled the rug from under COM too early. I understand the motivation (Business, revenues, etc...). The technology argument can be made on theorhetical grounds because nothing has been delivered. And while the theory sounds OK, there is still something amiss...

The class of applications that VFP is superior at building is not addressed by .Net. And for this reason, I think VFP is going to be around for a long while.

As for client/server, web-based , n-tier apps, etc... VFP still shines. COM has matured. It works. We understand it. The tires are kicked. Yes, .Net targets this stuff. However, you can deliver apps in VFP, and VB for that matter today. And for this reason as well, VFP will be around for a while.


My 2-cents..