Converting to and from VB and C#
The easiest way to convert from VB to C# or C# to VB is this: learn the language.
I am a BIG VB fan. I've been using VB for nearly 6 years, both VB6 and VB as a part of the .NET framework, and I get arround when it comes to VB. But I recently came across a problem when developing the ClubStarterKit, I needed to convert the whole solution into C# for those who want to use C#. So I got to thinking and I really didn't want to learn C# at the time. I just wanted to convert it and not deal with it any longer.
But here's the problem with that methodology: I started converting the VB solution into C# using my favorite converter (Econ NetVert) and there were errors... many in fact. So I tried to go in an figure out the various problems. I seemed to think there was just 1 solution that would fix all these problems at once and all I had to do was just take the time and make it work. But in my case, that didn't work so well.
So I already knew I was taking this Java class. Turns out that the syntax for Java is pretty similar to that of C#. The only difference I see is that the libraries are VERY different and some of the ways you get user input and what not is very different as well.
I'm learning Java but I am also sort of learning how C# works. It's starting to click and now I can look at a piece of C# code and think, "what does that do" and answer it!
Moral of the story: Learning a language is invaluable when you have to do converting. There really isn't any excuse the C# or VB guys can make to not know both languages. They are both VERY similar and I think converting between one and the other isn't hard as long as you take the time to go ahead and learn the language your are trying to convert it in. REMEMBER: C# and VB both convert to IL!
I think I am going to put in tips for those converting from C# to VB soon. I think that should help Rob Connery and some others figure out what this VB thing is :)