In 'Advantages of both languages' for C# you indicate 'using', but of course VB does have this since 2005.
Also, you might want to add 'Support for XML literals' on the VB side (in 2008), which is not available in C#.
On the C# side, you're missing 'anonymous methods', which isn't available in VB.
In the 'Keyword Differences' section, you state that C# has no equivalent to 'Shadows' - the C# equivalent is 'new'.
Also, for the 'Call Windows API' section, 'Declares' is the legacy approach (which is still allowed). The more standard .NET approach is an
empty 'Shared' method with the DLLImport attribute.
'AddressOf' in VB is totally unrelated to the unsafe C# '&' operator.
The built-in VB casting macros (CInt, CStr, etc.) are more accurately converted to the System.Convert methods, where they exist (e.g., CInt is better approximated in C# by System.Convert.ToInt32).
The VB 'DirectCast' macro is closer to the C# cast however.
You also might want to add an entry for TryCast (VB) and 'as' (C#) - these are equivalent.
C++ to C# Converter
C++ to VB Converter
C++ to Java Converter
Instant C#: VB to C# converter
Instant VB: C# to VB converter
Instant C++: convert VB, C#, or Java to C++/CLI
Java to VB & C# Converter: convert Java to VB or C#
Last Visit: 31-Dec-99 18:00 Last Update: 30-Jul-15 3:00