c# versus vb

[benmartin101]

currently, i'd say that i'm much more familiar with vb.net than c#.net. I am trying to decide whether to start using c# more often or just stick and learn even more about vb.net. Could you guys tell me the advantage of c# over vb? So far, to me...they seem the same except for the syntax and key words.

[techgnome]

Pretty much summs it up. For the most part, people's advise in this area is to tackle VB first, then move to C# at a later time. For what ever reason it's easier that way.

-tg

[kaihirst]

Hi,

I use both, and I would personally learn C# first of all.

This is due to the case sensetivity in C# and its strictness is similar to Pascal, so it would inevitably teach you better hadits that VB will as vb is not case sensetive, a little more laxed and flexible in its rulea dn boundaries of acceptable programming.

my 10p

ta

kai

[jmcilhinney]

Here's my advice: if there is something that you want to do that is easy in C# but not in VB.NET then you should consider switching. Otherwise, why bother? That's like saying "my car's fine but other people are driving that car so maybe I should sell mine and get one of those." If you want to learn C# to expand your horizons then I'd say that that's great and you should go for it. Other than that, there is no reason to move to C# unless you are finding that VB.NET is limiting you in some way. There are pluses and minuses on both sides, but the most obvious reason for switching that I can see is that C# makes the use of pointers much easier than VB.NET. The vast majority of applications don't require the use of pointers though, so that's not a compelling reason for most. C# also has operator overloading, but VB.NET gets that in 2.0 anyway.

[kaihirst]

Hi,

very true... but a bit small minded on that one but agreeable. When learning aprogramming language though you really should lok a the bigger picture. they all complete and fill ageneric void just the saem, but others do it in dirfference roads and roundabouts ( in a car sense...)

But if youve learned a programming language such as VB in most cases, you should stick to VB. BUT

if yo wnt to get serious in your programming, get strict and define and introduce standards in your work suhch as I did when learning Pascal as this was a very strinct language indeed.

so is C# so if your a serious programmer, wanting good standards and dont mind learning a lot and spenidn quality time in the drawing board, C#.

If you want ease of use. VB.NET

[Hack]

More of a general discussion topic than a code specific topic. Moved to General Developer.

[penagate]

Advantages of C#, well. How about we list the disadvantages of VB in comparison instead?

- Weird, archaic syntax. BASIC dragged into the OOP world. Does not work for me.
- Unable to create unsafe/unchecked code.
- No syntax for operations such as casting/dereferncing. Relies on functions.
- Less operators than C#. In particular, no conditional operator.
- For reasons unknown, still includes the mother of all program breakers, On Error Resume Next/GoTo.

A good comparison of syntax here.

Anyway, my biggest gripe is that it is an ancient language that Microsoft has tried to turn into C#. I see no reason why not to use C# itself instead

[GlenW]

No operator overloading (I think)

[penagate]

Not before .NET 2, anyway.

[tr333]

the main difference i see is that C# was the first language to be "designed for .NET", while vb/c++/java were all "converted" to .NET.

[Shaggy Hiker]

Enjoy the ; key.

There is little real difference where it matters. What matters to the end user is how it looks on the outside, and how it behaves. What is going on inside that pretty package is not something that most people dwell on until something goes wrong.

Hmmmmmm......ya know? That's how men see women, and vice versa!

But back to the topic. Most of the objections to VB here are more preference than substance. Penagates views are very real, but are not reasons to choose one language over another UNLESS you happen to share those views. None of them are significant to me, so I would never choose C# over VB for those reasons.

kaihirst points out the case sensitivity of C# as being a benefit. I find it to be a particularly annoying deficiency. You could have two variables i and I and they would be different things though they would have the same name. The only way to communicate on this (if you were foolish enough as to actually DO that), would be in writing. Someone would have to SEE the variable to know which one you are talking about. Furthermore, I use the case correction to my advantage. Add a capital letter somewhere in the variable name (different locations in different circumstances for me). Then, when you use the variable, if the capitalization is not corrected, you have the wrong variable. I find this useful when I have come back to some code after a sufficient abscence. Very trivial, I admit, but a slight edge in my opinion.

[benmartin101]

Other than the ones discussed here, such as operator overloading, etc...are there other things that vb.net can do that c#.net cant and vice versa? For instance, i've heard(and I may be wrong on this) that when making web application or web services...people use c#, why is that?

[dee-u]

This seems related to this thread...

[dee-u]

And this also...

[RobDog888]

Like other views, use the right tool for the job. If your looking to increase your skills for job hunting I'd suggest C# as its hot right now but things always change. It comes down to what your needs and reasons are.