Thanks Kamal for this info and for your work with VFPToolkit also.
I wonder if it wouldn't be better if VFP team CLEARLY said: "Hey people - direction is VB.NET you can work with VFP and C# but if you will use VFP and VB.NET your road will be more pleasant and we will support you in that direction more that in another"



>Hi Jozef,
>
>I use both VB .NET and C#. :) Most of my work till now is in C# except for the VFPToolkit for .NET which is available in both VB .NET and C#.
>
>If I have to recommend a VFP deveoper which language to pick of the two, that would be VB .NET. Two prime reasons:
>
>1. VB .NET has something which C# does not have today and we probably will never see it in C#. The Imports statement in VB .NET allows to import namespaces+classes. It is like doing a "SET CLASSLIB to a class in a library". This allows developers to create custom libraries (like the VFPToolkit) and access them as if it were a part of the core language.
>
>2. They already know the commands For-Next, If-End If, Do-While, For Each-Next etc.
>
>Kamal
>
>>Hi Kamal !
>>
>>Can you told us what do you prefer VB or C# ? (if it is not a secret :) )
>>
>>
>>>Also, I am not suggesting that you to pick VB .NET over C#. I am just laying the facts on the table.
>>>
>>>Kamal