Fantastic. Thanks for listing these.

>Visual Basic .NET is a much better choice for most VFP developers, only a short list of reasons below:
>
>With/EndWith - in VB.NET and not C#
>
>Late Binding Support – VB.NET natively supports late binding to objects
>
>More “Fox like” Event Binding – VB.NET offers the HANDLES keyword allowing you to handle the 80% of eventing cases where you just need to tie a method to its event.
>
>Parameter handling – VB.NET supports optional parameters – just like VFP
>
>Background compiler – The VB.NET background compilation engine allows its intellisense to provide more help as you’re coding – just like VFP
>
>Not case sensitive – Just like VFP
>
>VB.NET will continue to gain more and more VFP like features while C# probably won't.