>>.NET is not just a buzzword or a "marketecture." There is an actual specification and rules which must be followed. If you read up a bit on the Common Language Specification (for instance, at the site of the ECMA standards body or on MSDN) you will quickly see that VFP is not .NET compliant. For starters it cannot generate CLS code. Therefore renaming VFP to indicate that it is a .NET tool would be misleading, to put it charitably.
>
>This has nothing to do with my knowledge of .NET. I'm just responding to a request expressed by several members who also thought that it would be a good idea to get some feedback on it.


I see -- you had no choice but to start this thread. A novel defense. In any case, you have my feedback and my vote.

Mike