In my opinion, translating from VB.NET to C# or vice versa really isn't that difficult once you have a decent understanding of each language. I've been doing it since I started working with .NET almost a year ago learning both languages side by side. Obviously there are several differences, but the generalaties apply fairly consistently across the board. But...and you knew there was one coming...why should I have to manually translate from one language to the other when it can be done programatically? A damn good question for which the answer is "you shouldn't."

I just recently found an awesome little web application for translating C# to VB.NET (and VB.NET to C#) written by Carlos Aguilar (from Microsoft's IIS7 development team). My initial tests have proven very good results. Link to the app here.

He has a few other tools that might prove pretty useful:

• CodeColorizer
• WebChart Control - for creating charts in your .NET web pages
• UML Diagrams - generated straight from C# and VB.NET code

~tod

Disclaimer: I actually 'found' this app through one of my RSS feeds, but for the life of me cannot remember who...sorry.

tags: c# vb.net translate