>>>As Ken posted earlier, it's just VB now. the .Net has been dropped from just about everything. Only ADO.Net and ASP.Net remain.
>>>
>>>>Only that could direct me toward VB.Net instead of C#.
>>
>>So sad. They found a way to stop us from asking a VFP.Net version ;-)
>
>There is no benefit from a new .NET language called VFP.NET. For one, it would not be backward compatible with VFP 9.0 code, so what would the point me of having it exist. The other is, it would look much like VB.NET and would simply take away resources from the VB and C# teams in order to create and evolve it. We view VB as evolving into VFP.NET (in a sense), although the VFP team sees nothing wrong with using C# as your primary .NET programming language and we leave it up to developers to decide which .NET language is best for them to use (and many .NET developers use both VB and C#, to some degree).

I'm sorry I made you waste your time on that reply. I only made that reply as a joke. I already knew the reason why there will never be a VFP.Net

I guess that perhaps you wanted to make it also clear possibly to those VFP user not aware of those facts.