Convert .NET is an integrated, powerful, multi-purpose conversion and developer tool. Features: C# to VB and vice-versa, LINQ tester, Encryption/Decryption, Regular Expression tester, Base64 Encoding/Decoding and Full-text translation.
not perfect, but pretty good; - able to generate the structure perfectly - variable definition & loop & linq converted perfectly - didn't convert vb functions such as ucase, vbnewline, etc - didn't convert array index ie. () to 
Exactly what I was looking for. Online converts often can't handle Linq/Lambda Syntax. This one did the trick. It would be even better if it was directly integrated with VS, but it's good enough as is.
Seems like it perfectly handles even complicated conversions! I really like the integrated translation tool, although it seems not all string literals are localized (for example parts of the options are missing). Also the JSON explorer is very useful and would be even more so, if it was somehow possible to modify the object tree and write it back to the JSON file (like a visual designer). All in all a great tool! Keep up the good work!
This is a really neat project! We've got a ton of vb.net at my place of work and I have wanted to convert it to C# for the longest time, but there's a LOT of code. This will certainly help.
Some potential improvements for VB to C# language:
1) With statement in VB. Currently says it isn't supported in C#. That is correct, but the equivalent is an Object Initializer.
2) Use of IIF in VB.Net continued to use IIF in C#. While this is valid, it would be better to convert IIF to use a ternary statement (?:). Safer when doing type checks and evaluation.
3) Conversion of a string with embedded special characters (in this case a regex statement with \d) double-escaped the \. If these are in a string, I would recommend placing a @ at the start of the string instead. "\\d" would cause the regex matcher to fail while @"\d" would not.
4) This one is more of a semantics thing... In VB if you use OR as a logical operator (such as in an IF statement) then the equivalent in C# is a logical ||. OR when used in assignments would be | in C#. It works either way, fortunately, so its more of a semantics thing.
5) #End Region is not valid in C#, it should be #endregion.
6) Converting Windows Forms misses the initialization of the Event Handlers (since VB.Net does not require them).
This would be fantastic as an extension. But as a stand-alone application, the convenience is lost. I won't likely be using it every day, which means that when I actually need it I won't remember where it is, or I'll have to sift through a bunch of other junk to find it.
All that to say, since it's a stand-alone application, just using a browser to Google what I'm after is more convenient.
Consider turning this into a collection of dock-able windows within Visual Studio and you could have a hit on your hands. I'd pay for that. Open-source it or add a pluggable API so people can add other kinds of conversions. That would be brilliant.