>>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.
>
>Great Idea!!!!,
>I fully support it. No body from my customers interested that VFP do not use CLR. They like to use most advance technologies advertised by MS - .NET. VFP.Net is perfect sales and promotion trick, from which all FoxPro community will gain.

If you'll excuse the sexist remarks, you've gotta be able to look yourself in the mirror when you shave in the morning. As a professional, I'd hope that such misrepresentations of the product would be seen as unethical at best. Our job is to educate the client as to what aspects of technology are and are not important to them; much of the reason that my clients deal with me is that I'm an open book to them - I put my cards on the table and make certain that they understand that there is no hidden agenda. I'm encouraged when a client < intelligently > inquires why I suggest a non dotNet solution to them; it indicates that even though there's massive marketing of the sales concept out there, they trust me to explain what it really means and why it is or is not going to be important to them. I don't represent myself as infallible (I am not the Pope) but in the main, my clients trust me in the same way that they'd trust an attorney or an accounting auditor from Arthur Anderson... < g >