The C# team posts answers to common questions and describes new language features
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:
Catch ... When ...
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]
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
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 !!!