>I agree with your reasons that migrating to VB.NET from VFP will be easier than going to C#, but only for navigating the learning curve. In the long run, no matter what language you start off with, you'll most likely do well at both (or any other .NET languages that come out).

Mike, it is more than just a learn curve issue, it is an investment issue. While there are not all that many differences between VB .NET and C# (a few pros and cons for each), that will increase over time. VB .NET is not just a langauge, but an IDE (development enviroment with tools), so VFP developers should very seriously consider making VB .NET their primary .NET language when using VS .NET, but of course being able to read or even code C# as a secondary .NET language would be a good thing. To be clear, I am not attempting in any way to get VFP developers moving to VB .NET. What I am advocating is for those VFP developers using .NET to chose VB .NET over C# as their primary .NET language for their own best interests long term.