I’m not considering this – I’m comfortable with C# and VB, but an expert in neither. But, some on my team have expressed an intention to do this since we’re moving toward C# as a standard.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m not considering this – I’m comfortable with C# and VB, but an expert in neither. But, some on my team have expressed an intention to do this since we’re moving toward C# as a standard.
Hell’s no. Just an absolute waste of time.
I would use VB over C# (or C# over VB) only if the language enabled functionality that was not available in the other.
For example, making late bound calls to COM interop objects is much easier in VB than it is in C# (although that is going to change in C# 4.0).
That being said, I’d stick with the language that your team is using, or what you prefer (if that is an option).