>>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.
>
>How do you vote in this survey.
>
>Can another choice possible be added. How about Visual FoxPro for .Net ?
>
>"Create standalone desktop, n-Tier, and web applications with the ability to create and consume .Net web services allowing for seamless integration into any .Net project."
>
>...or something like that.
>
>Also, Didn't I hear the Delphi.Net wasn't going to be a CLR language?
>
>BOb

Hi Bob,

I second your amendment. Calling it VFP for .NET would be a big step in the right direction, and it addresses the concerns of the purists who insist that "VFP is not .NET". Personally, I think that is going overboard: a word invented by Microsoft's marketing department can mean whatever they like. There's no need to quibble over semantics. VFP is at least in some significant way a player in the .NET arena, is it not? Be up-front about exactly how this is true, and no one should feel they've been deceived by some shallow marketing ploy. The only thing that MS is marketing is .NET, so let's not be suicidal: VFP needs and deserves a piece of that marketing.

Mike