C#'s edge over VB [closed]

Answer 1

The big advantage i see with C# is that the vast majority of open source projects, sample code and blog snippets are written in C#. Although it’s easy to convert these to VB.NET with tools (or your head) it is still a monotonous task for VB devs (like me).

Even if you write in VB.NET day to day, you will still need to be able to read C#

Technically, they share the same framework with same performance and memory characteristics and same type systems, so I find it hard to hard to split the two.

Most good developers should be able to shift between the two with a few days adjustment time.

My core frustaration lies with the hundreds of time I have written:

String lastName as String

and wondered why it never compiles!

Answer 2

As I understand it, there are differences between the languages though they are minimal. I would suggest working with the language that you/your developers would feel most comfortable with. If they already have VB experience then I'd suggest VB.Net/vice-versa.

Though I prefer the terse syntax of C# personally. :)

Answer 3

Here is another point not yet covered in this trail:

Higher Degree of Employability + Better (more) Dev Resources

Now I don’t agree with this point of view however:

There are more C# dev shops that VB shops

Some backward c# employers will put you at a serious disadvantage if you are stronger with VB. So maybe C# is the better choice here.

On the flip side, when you go to hire people for your C# project, you will be able to attract more candidates to iterview and get better skills as a result – I don't think detail should be overlooked.

Answer 4

Street cred among geeks.

(And don't pretend that's not important!)

Answer 5

My favorite feature of C# that VB doesn't have is the yield statement. It lets you easily return an lazily evaluated IEnumerable from a method.

Here is an article that covers it: http://msdn.microsoft.com/en-us/magazine/cc163970.aspx

Answer 6

I have to say it's been my experience when using Google to search for examples or documentation that C# examples are of better quality than VB examples. This isn't to say that there aren't bad C# examples, but if you search for something like "dictionary drop down" adding C# will provide a better quality answer higher on the list.

This doesn't apply to examples that display both C# and VB code side by side.