>What are your views on the .Net language situation?

Microsoft has always said that it is a matter of personal preference, and I believe that to be true. When VS.NET came on to the scene, there really wasn't much difference between the languages at all. As they evolve, VB will continue to focus more on RAD capabilities, while C# gets new language features with perhaps more flexibility than VB counterparts. By learning one language, you'll be well on your way to being able to work with the other. As others have said, the complexity is in the .NET framework.

With its C heritage, experienced C, C++, and Java developers head straight for C#. It's also a stricter language, enforcing standards that may be optional in VB, perhaps resulting in higher-quality code. I think this is one reason why you see heavy OOP and disciplined types like Markus Egger and Kevin McNeish preferring C#. These guys kept a tight ship in VFP, and that's easier to do in C#. If you see yourself in that camp, then maybe C# is the language for you.

VB is more focused on RAD capabilities and getting the job done. This focus, along with similarities to the xBase language, makes VB feel more at home to most VFP developers, IMO. Of course, it's not home, it's .NET, so there will be a learning curve regardless of the language you choose. Still, VB might be an easier transition. At one point, it seemed that the Fox Team had more influence with the VB guys, meaning VFP-like features would more likely make their way into VB. I don't know if that's still true. With LINQ on the way, they may have had their effect on both teams.