Possible mistaken empty statement

When it comes to it, programming is a series of conventions. Different languages have different conventions. If you are used to one set, it will take time for the eye and brain to become accustomed to seeing conventions which are incorrect in the new language.

Yes, I know that the only difference between C# and VB net is a ; at the end of each line... here are some more that a programmer with a trained VB eye may find hard to spot.

Possible mistaken empty statement: error

This error message is raised when there is the following statement:

Example:

if ( some condition or other) ;

C# does not use a final ; on a branching statement (if etc)

Other conventions that may trap the experienced vb programmer

• Strings is an ambiguous reference between Microsoft.VisualBasic.Strings and System.Linq.Strings
• The best overloaded method match for string.Split params char has some invalid arguments
• cannot convert from string to char
• The name elseif does not exist in the current context
• Define a function in c sharp
• check if int is null
• vb eqivalent of unload or queryunload
• The left-hand side of an assignment must be a variable, property or indexer
• Possible mistaken empty statement