The C# vs VB.NET debate is as old as .NET itself, although thankfully appears to be calming down in recent years.
When I started using .NET over 10 years ago, I started with VB.NET because although I had 6 years C experience from a previous life, I was also experienced with VB6 and VBA, so it was a natural progression to get into VB.NET.
While its important to specialise, to focus in order to develop skills in particular areas, its also important to consider the best tool for a particular job, and most definitely not get involved in “religious” arguments, I bet a lot of which are fuelled by the developers concerned not knowing the other language very well (or their own main language if it comes to that) and also not wanting to somehow “lose” the investment in time they have made getting this far.
I have just browsed around the net looking for real information on the differences and most of what you read is just garbage. If a post starts with “I hate VB.NET” or “I hate C#”, for sure that person is unemployable in my eyes until they gain enough experience and perspective to be able to change their views in order to DO WHATEVER IS NECESSARY to produce the best possible system in all respects for their end user, irrespective of the technology required (I’ll bet a lot of people probably never get past this stage in their own personal development).
Having used .NET for over 10 years, probably C# 60%, VB.NET 40%, my specific views on the subject are as follows:
- C# became a standard outside of Microsoft in 2006. Wikipedia has some more information on this at http://en.wikipedia.org/wiki/C_Sharp_%28programming_language%29.
- By default the C# type system is better than VB.NET. If you use VB.NET make sure you turn option explicit on in the project settings along with option strict and ideally option infer as well. The benefit with option strict is that the compiler will pick up errors that otherwise would only detect at runtime, making VB.NET similar to C# in this respect. This is useful because type checking can be used to your advantage when writing or re-factoring code at compile time and it also helps produce errors and warnings (you are aiming for zero warnings aren’t you? If not seriously consider doing this as warnings can hide many larger errors).
- C# has some very succinct constructs, such as:var c = d ?? 0;andvar c = d as long?;
- More companies prefer C# to VB.NET, possibly for the above reasons and rates of pay are 15-25% higher for C#.
I’ll be blogging more about the features in future posts.
So I usually prefer C# if left to my own devices, but as related its important to remain impartial as well and to listen to other points of view, particularly your end users.