VB .NET vs. C#

So, how do you choose? If the functionality in the two languages is nearly the same, how do you go about choosing which language you want to use? I’ll break this discussion into three categories: familiarity, resources and support, and personal edification.

Familiarity

The main reason to choose VB .NET or C# is familiarity, which is interesting because both languages are new. I’ve had some people on the Microsoft project team tell me they don’t want the move from VB to VB .NET to sound like a big move. Well, it is a big move. The learning curve is steep. The learning curve from VB to C# is steep. The learning curve from C to C# is steep.

You’re learning a new language, but much of it is learning the .NET Framework and all the classes the CLR supplies. If you want to create a new thread, it’s in the run time. If you want to access data using ADO.NET, it’s in the run time. If you want to read in some XML, it’s in the run time. I think you get the picture: Much of what you will be doing is learning the run time.

As you learn the run time, however, you’ll be using some language to play with it. While VB .NET is a new language, and there are differences from VB that will cause you to lose your hair, I think it’s safe to say that the learning curve going from VB to VB .NET is less steep than it is from VB to C#. C developers will feel more at home with C# than with VB. If you are a hard-core Java or JScript developer, you also will feel much more at home with C#.

那个更熟悉?一言道破，C 用户到C＃以及vb到vb.net是个不错的选择。

VB developers will be much more at ease with VB .NET’s loops, conditional constructs, variable declaration syntax, and more. Why fight case sensitivity and that double-equals sign when you don’t have to? You’ll find yourself searching for a bug for an hour, and it will turn out to be a missing equals sign. You don’t need the headache of learning the nuances of a new language when you are trying to learn the CLR.