That's great except that we're here primarily to support and promote vfp (I would argue), not to support the marketing interests of MS$ and the fact that the primary presence of Microsoft here is marketing speaks volumes...
>Hi,
>Sorry for jumping in.
>
>My personality feel that, we don't keep "betting" Ken, because he also try very hard to market VFP, add new features and also great enhancement to VFP. Refer to wishlist, the willing to migrate VFP to .NET platform really is not that much. Therefore, as a marketing manager, Ken only do what customers need, because no demand then support is meaningless.
>
>Of course, everybody know that .NET is "future". Myself also start learning .NET in order to not leave behind. However, if VFP become VFP.NET, would VFP can be as flexible as current? What is the pros/cons if migrate VFP to .NET? Is it really what we need?
>
>If "VFP.NET" cannot offer the strength like VFP8, then what the point to migrate? Why don't just start learning C#? Since, 80% if code will be the same. Do you want to do so hard just because of that 20%?
>
>I am not sure I am correct/wrong, I just hope we don't "force" ken too much.
>
>Anyway, I am looking for "VFP.NET" if it doesn't lose VFP strength....
>
>Nice day