>I was particularly struck by this line in Ken's blog post :
>
>" But by the time VFP 9.0 was released, the amount of sales for all versions of VFP combined annually was less revenue than Microsoft sales of Visual Studio in only one day. "
>
>I have to say that the further I get into .NET 4.0 ( the VFP 6.0 of .NET <g> ) the more I "get" why the strategy to move from COM and GDI made good sense. I think what a lot of our Fox community misses is that there were a lot of reasons besides its imminent demise why many top level Fox developers migrated to .NET over the last ten years. I'd be interested to know how former successful VFP developers who have made the transition to successful .NET developers would feel about going back to the VFP paradigm even if VFP were a supported product at MS.
>

I wouldn't use it again.

VFP was great for developing windows apps, and really was excellent when combined with SQL Server.

.NET can make windows apps that far outshine VFP in user interface, and the classes available are mind-boggling.

With a lot of kludging, VFP with third party frameworks can be hacked into a web application. Sorry - not my style.

If the etechnologia stuff had actually been functional and supported several years ago, that might have made using VFP worthwhile in some cases, but on its own it really doesn't cut it for modern development except for perhaps quick and dirty jobs.