which is best C# or VB.Net

C# is better than VB.NET.It is my personal opinion.

As far as language and features are concerned mostly both are same.

At the end of the day, it actually comes down to personal preference. Try each and see which you get on with better. As Maciej says, each have merits and each have faults.

Some would say VB.Net is easier to pick up, but it depends on your background in programming. If you are coming from a c/c++ background then you might find C# easier.

As i had mentioned in comment, both have their merits and faults. All depends of your needs...

See these articles:
http://en.wikipedia.org/wiki/Comparison_of_C_Sharp_and_Visual_Basic_.NET[^]
Complete Comparison for VB.NET and C#[^]
and decide which is best for you ;)

Cheers!

The one that you know best, and are most comfortable in.

Pretty much, anything you can do in C# you can do in VB, and vice versa - and the stuff you can do in VB that you can't in C# you don't really want to anyway! C# has strong typing, which can be a major plus when it comes to reliability, but VB is more forgiving so it's easier to write.

Pick the one you are happiest with, and don't worry about the "VB is a language for children" claims. It isn't - but I use C# by preference anyway!

While they are similar, C# is better.

If you really want to explore, then go through the below articles.

1. Comparison of C Sharp and Visual Basic .NET[^].
2. Complete Comparison for VB.NET and C#[^].
3. VB.NET and C# Comparison[^].

4. 10 Reasons Why Visual Basic is Better Than C#[^].
5. Top 10 reasons C# is better than VB.NET[^].

6. What are the advantages of C# over VB.NET and vice versa?[^]

C# is better than VB.NET

because

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
And again We can’t say that Vb.Net is not preferred it has it’s own advantages over C#


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 (ie. 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.