What are the advantages of C# over VB.NET and vice versa?

What are the advantages of C# over VB.NET and vice versa?

Rate This
  • Comments 42

The choice between C# and VB.NET is largely one of subjective preference. Some people like C#'s terse syntax, others like VB.NET's natural language, case-insensitive approach. Both have access to the same framework libraries. Both will perform largely equivalently (with a few small differences which are unlikely to affect most people, assuming VB.NET is used with Option Strict on). Learning the .NET framework itself is a much bigger issue than learning either of the languages, and it's perfectly possible to become fluent in both - so don't worry too much about which to plump for. There are, however, a few actual differences which may affect your decision:

VB.NET Advantages
  • Support for optional parameters - very handy for some COM interoperability
  • Support for late binding with Option Strict off - type safety at compile time goes out of the window, but legacy libraries which don't have strongly typed interfaces become easier to use.
  • Support for named indexers (aka properties with parameters).
  • Various legacy VB functions (provided in the Microsoft.VisualBasic namespace, and can be used by other languages with a reference to the Microsoft.VisualBasic.dll). Many of these can be harmful to performance if used unwisely, however, and many people believe they should be avoided for the most part.
  • The with construct: it's a matter of debate as to whether this is an advantage or not, but it's certainly a difference.
  • Simpler (in expression - perhaps more complicated in understanding) event handling, where a method can declare that it handles an event, rather than the handler having to be set up in code.
  • The ability to implement interfaces with methods of different names. (Arguably this makes it harder to find the implementation of an interface, however.)
  • Catch ... When ... clauses, which allow exceptions to be filtered based on runtime expressions rather than just by type.
  • The VB.NET part of Visual Studio .NET compiles your code in the background. While this is considered an advantage for small projects, people creating very large projects have found that the IDE slows down considerably as the project gets larger.
C# Advantages
  • XML documentation generated from source code comments. (This is coming in VB.NET with Whidbey (the code name for the next version of Visual Studio and .NET), and there are tools which will do it with existing VB.NET code already.)
  • Operator overloading - again, coming to VB.NET in Whidbey.
  • Language support for unsigned types (you can use them from VB.NET, but they aren't in the language itself). Again, support for these is coming to VB.NET in Whidbey.
  • The using statement, which makes unmanaged resource disposal simple.
  • Explicit interface implementation, where an interface which is already implemented in a base class can be reimplemented separately in a derived class. Arguably this makes the class harder to understand, in the same way that member hiding normally does.
  • Unsafe code. This allows pointer arithmetic etc, and can improve performance in some situations. However, it is not to be used lightly, as a lot of the normal safety of C# is lost (as the name implies). Note that unsafe code is still managed code, i.e. it is compiled to IL, JITted, and run within the CLR.

Despite the fact that the above list appears to favour VB.NET (if you don't mind waiting for Whidbey), many people prefer C#'s terse syntax enough to make them use C# instead.

[Author: Jon Skeet]

Leave a Comment
  • Please add 6 and 4 and type the answer here:
  • Post
  • PingBack from http://www.indika.info/?p=4

  • PingBack from http://www.keyongtech.com/510075-the-demise-of-c/5

  • PingBack from http://softwareplusplus.wordpress.com/2009/04/19/a-managers-retrospective-on-the-c-versus-vbnet-decision/

  • You forgot to mention the "yield" keyword in C#. Missing yield in VB has made my life into hell now our projectmanager wisely made us convert to VB.

  • I our days most people use the .NET Framework to write 'Enterpise Level - Data Driven Applications' that rarely require advanced programming features and techniques. So when an 'upgrading' developer (new to VS) has to deside which language is the most appropriate, the one that has the most intellisense support and is most readable to the human eye will make the difference when code extends to some ten of thousands of lines. Only past experience, training and current working environments create the exception to the above rule.

  • I just recently made the change from VB to C# in <a href="http://www.juggle.com/microsoft">Microsoft</a> .Net.  I came from a Java background so C# really isn't too much different as far as syntax, but after learning VB I liked it a lot better.  I think VB is easier to ready and flows out a little better while coding.  I was hesitant to make the switch to C#, but it hasn't been too bad.

    There are definitely advantages to both languages.  I have found that Visual Studio seems to be a little better integrated with VB, but C# offers nice ways to consolidate code.

    It's always going to be an ongoing debate, but in the end a programming language is a programming language.  Syntax you can learn, but it's the logical thinking behind it that counts.

  • VB.Net is easy to do the coding, but when comes into performance VB relally go backwards than other languages such as Java/ C++, Is microsoft really considering the performance of the language?

  • VB's "Select Case" is more useful than "switch" because of the way in which the selected element is evaluated.  Also, its much more self-documenting and easier to read.

  • my qestion is which will be simpler to do a .net programe simpler and easier

  • my qestion is which will be simpler to do a .net programe simpler and easier

  • Hi, I've been using both of these languages. VB.NET and C# is just the matter of the language, but the most important thing is the core of .NET Framework. But I think since we working on this level with software implementation, I do believe that we should take care of the source code as well so it could be readable. Thanks

  • 1. Why do I have to type semicolon ( ; ) after EVERY command EVEN 99% of them are on single line ?

    2. Would you mind if someone tells you that "You" <> "you" ?!

    3. Did you ever find yourself looking for the missing Braces ( }}}}}} )  in the code?

    My suggestion, if you know English choose VB !

    c# will vanish !!!

Page 3 of 3 (42 items) 123