Mark,

That was the point of my proviso, "...whatever MS is calling the premier developer toolset it promotes, supports, and sells". If .NET is less than totally successful, Microsoft will just invent a new buzz-word, and that will become their new flagship, and we want to be a part of it. For now, yes, I'll gladly take the chance of being associated with .NET rather than the alternative being presented to us.

As to "what would the difference be between VB.NET and VFP.NET?", I think you must have misunderstood me. What would be the difference between VB.NET and VFP? Plenty. Nothing changes when you simply rename VFP to VFP.NET, and that is all I'm suggesting. Europa wishlist? OK, that's better than nothing, but I ask again "why wait?" I would gladly postpone the release of VFP 8.0 however long it takes for them to reprint the boxes, or whatever it takes to make the switch. One thing is for sure, they don't have too much promotional material to rewrite! ;-)

Mike

>Obviously, MS is putting an enormous effort into marketing .NET even now through its User Group strategy. So the premise I am about to toss out will probably not happen, but what if .NET flops and another direction is taken by the market/MS? Do you want VFP.NET saddled with this? Besides, I believe the managers at MS really do understand the strong ties VFP has to the .NET framework. We are starting to see better integration with .NET even more in VFP8. Besides, what would the difference be between VB.NET and VFP.NET? Syntax. So why have two nearly identical products? Now is definitely the time to get your ideas into the Europa wishlist, I just suggest everyone be careful what you wish for and think all this through carefully.
>
>>Michel,
>>
>>That's a great idea! But why wait for VFP 9.0? And let's also add a proviso that whenever it happens, it be VFP.x, where .x is whatever MS is calling the premier developer toolset it promotes, supports, and sells. Also understand that the appelation VFP.NET means nothing as far as VFP itself is concerned. We need not assume that VFP.NET in any way implies a redesign around the CLR. This is purely an act of marketing, and an expression of sincere commitment to a reasonably large number of long-time Microsoft customers. MS has assured the VFP community it is not planning to crush VFP or force us to switch to .NET unless and until we're persuaded that this is the best course to take, right? What would it cost to change the name from VFP to VFP.NET? I strongly believe that the benefits to Microsoft of such a change would be well worth the cost.
>>
>>Mike