>>For the little that I know about .NET, it seems to me that VB is more similar to the VFP approach than C#. I think that if one comes from VFP and have little experience in C and C++, you'd better go with VB.
>
>Not necessarily. I do VFP and C#. If pressed, I could do VB.NET too but I prefer C# as being sufficiently different in syntax from VFP to avoid confusion when switching from one to the other in the same day of work.

Same here, plus VB.NET syntax is kinda weird too.

I remember as .NET was about to be released, many VFP gurus said to use C# since that was where all of the resources were going and what the framework was written in, plus the language was pure which no legacy compromises. But later after .NET was released and more and more VFP gurus and started to lean towards VB.NET because of the focus on RAD.