>MENE, MENE, TEKEL, PARSIN
>
< snip >
Phew. Finally (at last) I have read it! I only wonder why you did not make this as an article for some of the VFP magazines.

What are the facts:

1. There are much more VB and VC (also Java) developers than the VFP ones.
   VB.NET and C# are with common syntax to the first group.


2. There is VFP Toolit for .NET written in VB.NET and in C#


3. There is no VFP.NET. Though MS announces that VFP7 IS PART of VS.NET, VFP7 is separate ... tool (blah, I said it) and VFP7 is NOT CLR BASED.


4. VFP8 Beta is out there, but is not so much promoted as the VS.NET (I even was not able to find information about VFP8 Beta on the MS site, today on 08.Oct.2002)

To summarize:
There are new versions of VFP, so VFP is not dead (yet).

However MS policy (according to me) is driving at .NET domination over all other development platforms (including VFP).

For VFP developers there is .NET Toolkit to help them get accustomed with the .NET platform, however if we wish to migrate to .NET we should learn VB.NET or C# (or some other .NET language) but I will suggest VB.NET is good choise, because its syntax is much common to VFP, than the syntax of other .NET languages. On the other hand, there are relatively much more samples for C# than for VB.NET, so knowing C# will be a plus.

To keep VFP alive, we should keep developing on it, and to make good interoperability and alternative services of the .NET ones.

Personally I am studing ASP.NET WebForms with the idea to make VFP builders with which to be possible to convert an existing VFP form to WebForm, but keeping the business logic and data access in VFP classes.

Kind Regards