VB to C# net guide

Ok so both of these referenced object libraries contain the Stings object. Soutions:

We can remove one of the references from our project (ideally we would like to get rid of the VisualBasic reference - that would make it more c# like.

We could just qualify the object libriaries so there is no ambiguity.

We need to keep the Linq refrences, How can we get rid of the VB references?

We may have code like the following:

Information.UBound(saSplitLine)
This can be replaced by:
saSplit.GetUpperBound(0)

or

Constants.vbCrLf as in

string[] saSplitLine = sText.Split(Constants.vbCrLf);

which can be replaced by:

char[] delimiters = new char[] { '\r', '\n' };
string[] saSplitLine = sText.Split(delimiters, StringSplitOptions.RemoveEmptyEntries);

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