>I heard a few public opinions on which VS.NET language is better and better from VFP developers. At Essential Fox, Ken said that VB.NET is better since it is more familiar to the VFP developers and C# is too rigid. Last year at Double Impact Markus said that C# is more elegant and Rick said that VB.NET was richer.
>
>Personally, I think I'm going to pursue C# for a few reasons:
>- it is more different that VFP and I won't confuse the syntax
>- I used to use C in University almost 15 years ago. With VB, I've always been a novice
>- I want to catch onto something completely new

IMO there is no "right" answer. It's one of the strengths of .NET, I think, that you can try both, settle into the one you like the best, but you haven't lost anything by trying the other. You can even mix and match, so if you like how VB.NET does somethings, then mix VB.NET into your C# code. And vice versa.

That said, some people will respond to VB.NET because a) they have already used VB, b) it's similar to VFP and so is more approachable.

In my experience, I prefer C#. VB.NET is *too* close to VFP. Since C# is so different, it's actually been easier to learn. One benefit of the Toolkit is that it's a great way to compare and contrast the two syntaxes. Now that I have the Toolkit and conversion tools, I know I'll be better able to grok the VB.NET mindset.

The conversion tools are

Kamal's:
http://www.kamalpatel.net/ConvertCSharp2VB.aspx

And another:
http://www.aspalliance.com/aldotnet/examples/translate.aspx