Hi John I agree with you on that has I said My first bet on .NET was C# I even bought a bokk callen Inside C# from Microsoft (very good book) but once I start getting more input I now thing that VB.NET is a more good bet even for VFP developers since the syntax is more like VFP wehn defining classes an methods.

>Hi Alexandre..
>
>Keep in mind that my response to Mark, with regard to the differences between C# and VB was in the context of Windows Forms. How you work with windows forms - whether you use C# or VB is essentially the same.
>
>With that said, your points about the differences that do exist between VB and C# are well taken. For instance, I can declare a read/write public property in VB with one line of code. In C#, I have to manually create the property get/set procedures. The case sensitivity is another important distinction.
>
>IMO, the curly braces, having to end lines with a ; and related items are archaic concepts. To me, a langauge should make your job easier, not more difficult. If and when I need to drop down to do low-level framework operations, it may very well be that C# is the ticket. First, I will give it a go with VB.
>
>Thanks for the input...