>I just ran over it, and found that for me it is not really a yes-or-no-question. I wouldn't want it to be a "fake". In my opinion VFP is not .NET; it has a different approach and qualities. However there is no
>need for VFP to hide itself behind a big name. .NET developers might want to try it out and soon realize
>"What the hell does this have to do with .NET" - They would never get into it deep enough to see its possibilities and qualities as a middle tier development platform or cheap but powerful database.
>
>On the other hand we (VFP-developers) will definitely loose (or not get) contracts in the near future because
>decisions sometimes are in fact being made on the golf course. In this context VFP could gain "reputation"
>just by having this new name.

See the Montreal thread created yesterday in the User Groups category. This is where the request came from.