Comparison of C Sharp and Visual Basic .NET

C# and Visual Basic .NET are the two primary languages used to program on the .NET Framework.

Language history

C# and VB.NET are syntactically very different languages with very different histories.

As the name suggests, the C# syntax is based on the core C programming language originally developed by Dennis Ritchie at Bell Labs (AT&T) in the 1970s.[1] Java and C++ are two other programming languages whose syntax is also based on the C syntax,[2] so they share a common look and feel. See Comparison of Java and C Sharp for more on this topic.

VB.NET has its roots in the BASIC language of the '60s with its name being an acronym for "Beginner's All-purpose Symbolic Instruction Code". In its beginning, BASIC was used in the college community as a "basic" language for first exposure to computer programming and the acronym represented the language accurately. In the '70s, the language was picked up by microcomputer manufacturers of the era to be used as both a simple ROM embedded programming language as well as a quasi operating system for input/output control. In the early '80s, the language was picked up by Microsoft and expanded significantly beyond its original intent into their "Visual Basic" language/platform that was sold throughout the 1990s as a "rapid application development" (RAD) tool for Windows programming.[3] It competed directly against other RAD tools of the 1990s such as PowerBuilder.[4] Even though Visual Basic was a successful development platform, it was discontinued after its 6th version (VB6) when Microsoft introduced the .NET Framework and its related Visual Studio development platform in the early 2000s. At that time, the current C++ and VB6 languages were used by Microsoft as the basis for two new programming languages in their new "Integrated Development Environment (IDE)". These languages were named C# and VB.NET

Language comparison

Though C# and VB.NET are syntactically very different, that is where the differences mostly end. Microsoft developed both of these languages to be part of the same .NET Framework development platform. They are both developed, managed, and supported by the same language development team at Microsoft.[5] They compile to the same intermediate language (IL), which runs against the same .NET Framework runtime libraries.[6] Although there are some differences in the programming constructs (discussed further below), their differences are primarily syntactic and, assuming one avoids the Visual Basic "Compatibility" libraries provided by Microsoft to aid conversion from VB6, almost every command in VB has an equivalent command in C# and vice versa. Lastly, both languages reference the same Base Classes of the .NET Framework to extend their functionality. As a result, with few exceptions, a program written in either language can be run through a simple syntax converter to translate to the other. There are many open source and commercially available products for this task. The only fundamental differences between the languages can be found in the implementation of interfaces and in the declaration, raising and handling of events. Although both languages are high-level programming languages, VB.NET maintains a slightly higher level of abstraction in some respects.

Runtime multi-language support

One of the main goals of .NET has been its multi-language support. The intent of the design was that all of the various Microsoft languages should have the same level of access to all OS features, should be able to expose the same level of power and usability, and simplify calling from a module in one language to that written in another language.

In implementation, all .NET programming languages share the same runtime engine, uniform abstract syntax tree, and Common Intermediate Language. Additionally all .NET languages have access to platform features including garbage collection, cross language inheritance, exception handling, and debugging. This allows the same output binary to be produced from any .NET programming language.

Development environment

Visual Studio provides minor differences in the development environment for C# and VB.Net. With each subsequent release of Visual Studio, the differences between development environments for these languages have been reduced. For instance early versions of Visual Studio had poor support for Intellisense in C# compared to Visual Basic .NET, and did not offer background compilation for C#.[7] Currently, the main differences in the development environments are additional features for Visual Basic .NET that originated in VB6, including:

Background compilation is a feature of the Visual Studio IDE whereby code is compiled as it is written by the programmer with the purpose of identifying compilation errors without requiring the solution to be built. This feature has been available for Visual Basic since .NET 1.1 and was present in early versions of Visual Studio for Visual Basic .NET. However, background compilation is a relatively new concept for Visual C# and is available with service pack 1 for Visual Studio 2008 Standard Edition and above. A distinct disadvantage for C# is that the Error List panel does not update until the solution is rebuilt. Refactoring large projects in C# is made more difficult by the need to frequently rebuild the solution in order to highlight compilation errors.[8] Such is not the case with Visual Basic because the Error List panel is synchronized with the background compiler.

Background compilation is less demanding on system resources and results in faster build cycles.[8] This is a particular advantage with large projects and can significantly reduce the time required to start debugging in the IDE.[8]

Language features

The bulk of the differences between C# and VB.NET from a technical perspective are syntactic sugar. That is, most of the features are in both languages, but some things are easier to do in one language than another. Many of the differences between the two languages are actually centered around the IDE.

Features of Visual Basic .NET not found in C#

Features of C# not found in Visual Basic .NET

Other characteristics of Visual Basic .NET not applicable to C#

Dim i As Integer = "1" 'Compiler automatically converts String to Integer
Dim j As String = 1 'Compiler automatically converts Integer to String
If i = j Then 'Compiler does cast and compare between i and j
    MsgBox("Avoid using, but this message will appear!")
End If

It should be noted that although the default is for Option Strict to be off for backward compatibility reasons, it is recommended by Microsoft[15] and widely considered to be good practice to turn Option Strict on, due to the fact that it increases application performance and reduces the possibility of naming errors and other programming mistakes.[16]

Other characteristics of C# not applicable to Visual Basic .NET

Syntax comparisons

Visual Basic .NET terminates a block of code with End BlockName statements (or Next statements, for a for loop) which are more familiar for programmers with experience using T-SQL. In C#, the braces, {}, are used to delimit blocks, which is more familiar to programmers with experience in other widely deployed languages such as C++ and Java. Additionally, in C# if a block consists of only a single statement, the braces may be omitted.

C# is case sensitive while Visual Basic .NET is not. Thus in C# it is possible to have two variables with the same apparent name, for example variable1 and Variable1. Visual Studio will correct (make uniform) the case of variables as they are typed in VB.NET. In some cases however, case sensitivity can be useful. C# programmers typically capitalize type and member names and leave field and variable names lowercase. This allows, for example, a fairly natural naming of method arguments: public int CalculateOrders(Customer customer). This can, however, cause problems for those converting C# code to a case-insensitive language, such as Visual Basic, or to those unaccustomed to reading a case sensitive language.


Visual Basic is not case sensitive, which means that any combinations of upper and lower case letters in keywords are acceptable. Visual Studio automatically converts all Visual Basic keywords to the default capitalised forms, e.g. "Public", "If".

C# is case sensitive and all C# keywords are in lower cases.

Visual Basic and C# share most keywords, with the difference being that the default Visual Basic keywords are the capitalised versions of the C# keywords, e.g. Public vs public, If vs if.

A few keywords have very different versions in Visual Basic and C#:

Some C# keywords such as sealed represent different things when applied to methods as opposed to when they are applied to class definitions. VB.NET, on the other hand, uses different keywords for different contexts.


C# Visual Basic .NET
// Single line comment

/* Multi-line comment
   line 2
   line 3 */

/// XML single line comment

/** XML multi-line comment
    line 2
    line 3 */

   multi-line comment via pre-processing 
   line 2
   line 3
' Single line comment

''' XML 1st line comment
''' XML 2nd line comment
''' XML 3rd line comment

   multi-line comment via pre-processing 
   line 2
   line 3
#End If

Intra-line comments not available


C# Visual Basic .NET
if (condition) {
    // condition is true 
} else if (othercondition) { 
    // condition is false and othercondition is true
} else { 
    // condition and othercondition are false 
If condition Then 
    ' condition is true
ElseIf othercondition Then
    ' condition is false and othercondition is true
    ' condition and othercondition false
End If


C# Visual Basic .NET
for (int i = 0; i < number; ++i) {
    // loop from zero up to one less than number
For i As Integer = 0 To number - 1
    ' loop from zero up to one less than number
for (int i = number; i >= 0; --i) {
    // loops from number down to zero
For i As Integer = number To 0 Step -1
    ' loops from number down to zero
for (int i = 0; i <= 20; i += 2) {
    // loops from 0 to 20 by 2's
For i As Integer = 0 To 20 Step 2
    ' loops from 0 to 20 by 2's
break; //breaks out of a loop
Exit For 'breaks out of a for loop
Exit While 'breaks out of a while loop
Exit Do 'breaks out of a do loop


Primitive types

C# Visual Basic .NET
if (a == b) {
    // equal
If a = b Then
    ' equal
End If
if (a != b) {
    // not equal


if (!(a == b)) {
    // not equal
If a <> b Then
    ' not equal
End If


If Not a = b Then
    ' not equal
End If
if (a == b & c == d | e == f) {
    // non-short-circuiting boolean operators
If a = b And c = d Or e = f Then
    ' non-short-circuiting boolean operators
End If
if (a == b && c == d || e == f) {
    // short-circuiting boolean operators
If a = b AndAlso c = d OrElse e = f Then
    ' short-circuiting boolean operators
End If

Object types

C# Visual Basic .NET
if (object.ReferenceEquals(a, b)) {
    // variables refer to the same instance
If a Is b Then 'Can also be written as If Object.ReferenceEquals(a, b) Then
    ' variables refer to the same instance
End If
if (!object.ReferenceEquals(a, b)) {
    // variables do not refer to the same instance
If a IsNot b Then
    ' variables do not refer to the same instance
End If
if (a == b) {
    // instances are equivalent
If a = b Then
    ' instances are equivalent
End If
if (a != b) {
    // not equivalent
If a <> b Then
    ' not equivalent
End If
var type = typeof(int);
Dim type = GetType(Integer)
if (a is b) {
    // types of a and b are compatible
If TypeOf a Is b Then
    ' types of a and b are compatible
End If
if (!(a is b)) {
    // types of a and b are not compatible
If Not TypeOf a Is b Then
    ' types of a and b are not compatible
End If

Adoption and community support

Both C# and VB.NET have high adoption rates, and very active developer communities and Microsoft fully supports both communities. .NET Framework developers widely use both VB.NET and C# as primary languages.[17][18] However, C# has more community activity on the Internet and there are more books available for C#. This may indicate either that there is more adoption of C# or that users need more help with it.

Examples of community and industry adoption include:

Other languages

C++/CLI (formerly Managed C++)

C++/CLI (a replacement for Managed Extensions for C++) does not have the adoption rate of C# or VB.NET, but does have a significant following. C++/CLI syntactically, stylistically, and culturally is closest to C#. However, C++/CLI stays closer to its C++ roots than C# does. C++/CLI directly supports pointers, destructors, and other unsafe program concepts which are not supported or limited in the other languages. It allows the direct use of both .NET code and standard C++ code. C++/CLI is used for porting native/legacy C++ applications into the .NET framework, or cases where the programmer wants to take more control of the code; but this control comes at a significant cost of ease of use and readability. Many of the automated tools that come with Visual Studio have reduced functionality when interacting with C++ code. This is because reflection cannot provide as much information about the code as it can for C# and


J# runs a distant fourth in terms of adoption. J# is a language primarily designed to ease the transition of Java applications to the .NET framework; it allows developers to leave much of their Java or J++ code unchanged while still running it in the .NET framework, thus allowing them to migrate small pieces of it into another .NET language, such as C#, individually. J# does not receive the same level of updates as the other languages, and does not have the same level of community support. For example, Visual Studio 2005 Team System supports automatic generation of Unit Tests in C#, VB.Net, and C++, but excludes J#. J# has been discontinued and is not included in Visual Studio 2008 or newer versions, since the existing J# feature set largely meets customer needs and usage of J# is declining.

Additional .NET languages

Main article: List of CLI languages

All .NET languages compile down to Common Intermediate Language (CIL), which contains rich metadata and is functionally and logically equivalent to the original .NET language code. For these reasons, while it is possible to code directly in CIL, it is rarely done. The equivalency of CIL to .NET language code permits tools such as .NET Reflector to transform a .NET assembly into source code that is nearly identical to the original source. Code obfuscators are often used to guard against this, and operate by directly modifying the CIL of an assembly in order to make it difficult or impossible to de-compile to a higher level .NET language.


  1. "Chistory". Retrieved 2013-08-18.
  2. "History of Java programming language". Retrieved 2013-08-18.
  3. "The Birth of Visual Basic". Retrieved 2013-08-18.
  4. "Powersoft History PowerBuilder History". Retrieved 2013-08-18.
  5. Krill, Paul (2009-02-27). "Microsoft converging programming languages | Developer World". InfoWorld. Retrieved 2013-08-18.
  6. "Microsoft Intermediate Language". Retrieved 2013-08-18.
  7. Matthew Gertz. "Scaling Up: The Very Busy Background Compiler". MSDN Magazine. Retrieved 2008-12-16.
  8. 1 2 3 "System and methodology providing compiler-assisted refactoring". Retrieved 24 February 2015.
  9. Jonathan Allen. "Does C# Need VB9's XML Literals?". Retrieved 2009-01-13.
  10. "DateAndTime.Now Property (Microsoft.VisualBasic)". 2015-02-18. Retrieved 2015-02-24.
  11. "Development with My (Visual Basic)". 2015-02-18. Retrieved 2015-02-24.
  12. "Early vs. Late Binding". Retrieved 24 February 2015.
  13. "Try...Catch...Finally Statement (Visual Basic)". 2015-02-18. Retrieved 2015-02-24.
  14. "VB Catch ... When: Why so special? - The Visual Basic Team - Site Home - MSDN Blogs". Retrieved 2015-02-24.
  15. "Option Strict Statement". 2015-02-18. Retrieved 2015-02-24.
  16."Option Strict On". Retrieved 24 February 2015.
  17. 1 2 "VB and C# Coevolution". MSDN. Retrieved 2010-03-27.
  18. 1 2 "Mono brings Visual Basic programs to Linux". Linux-Watch. Retrieved 2010-03-25.
  19. "C# is rated higher than Visual Basic for the first time in history". Retrieved 24 February 2015.
  20. 1 2 3 Patrick Meader. "C#'s Exploding Mindshare". Visual Studio Magazine, November 2007. Retrieved 2008-12-16.

External links

This article is issued from Wikipedia - version of the 11/29/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.