Michel,

>In the very long thread started last night about various topics in regards to user groups and related activities, it came in the subject that it would be interesting to know who would be in favor of having the VFP 8 naming to be geared toward .NET. As the product integrates extremely well with .NET, several members came to the conclusion that it could well be represented in the name. This would not entail any functional changes to the product, but purely a change in the way that VFP is presented and marketed. Instead of being an adversary of .NET, VFP would become a part of it, thereby changing both people's perception of VFP and the VFP community's perception about .NET. You are invited to cast your vote. This will be greatly appreciated.

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.