We recommend n vb. NET to C # (C # To VB.net) Code Conversion (interchange) tools.

Below are n VB. NET to C # (C # To VB.net)CodeConversion (interchange) Tool

1. http://www.kamalpatel.net/(the most commonly used, but cannot be converted to a hexadecimal INT)
Online version: VB. NET => C # => VB. NET
Offline version: C # => VB. NET

2. http://csharpconverter.claritycon.com/(recommended! It is very easy to use, and there is almost no major problem .)
Online version: C # => VB. NET
Offline version: C # => VB. NET

3. http://www.ragingsmurf.com/
Online version: C # => VB. NET

4. http://aspalliance.com/
Online version: C # => VB. NET

5. http://developerfusion.com/
Online version: VB. NET => C # => VB. NET

# Develop in 6.www.icsharpcode.com has the conversion function.

If you have any other comments, let me know.
Finally, let's get the most useful one: Haha, you will know after reading it.
Http://www.4guysfromrolla.com/webtech/012702-1.shtml

From: http://ike.126.com

Flower spring Finishing
Or C #1.0. net is easy to translate, As long as unsafe, volatile and a few of the syntax not supported by VB (such as the event attribute, field target attribute on event, re-implemented interface, is a feature rarely used in general cases ). In VB, C # does not support many features and is commonly used. Therefore, the probability of successful translation is relatively low.

C #2005 has many more features that are difficult to translate into VB. Similarly, vb2005 also makes mutual translation less and less meaningful in the future.