Benefits of VB.NET over C#?

[Robert]

For a new programer, what would be the benefit of learning VB.NET over C#?

 

[William Ryan]

If you are a brand new programmer, VB.NET is widely considered to be the
more 'productive' langauge. It's not case sensitive so you get a lot more
out of intellisense. If you have a C langauge background though, C# might
be easier to learn. The main thing with VB.NET is the case sensitivity
issue and intellisense, although many consider the entire syntax easier to
learn.

When it's all said and done, learn whatever one you like better. They each
have a few subtle benefits over the other, but at the end of the day, they
are virtually identical in functionality. Morever, I'd focus on learning
the Framework, that's the hard part. The syntax is trivial from there. A
top notch C# Programmer can learn VB.NET in no time and vice versa...
However a Top Notch VB6, VC++6.0 programmer will have to spend a good bit of
time learning either .NET langauge, not b/c of syntax as much as
functionality....especially ADO.NET.

Ideally, learn them both, and write code in them both so you can comfortably
flip between them, then your career options will be the widest.

HTH,

Bill

 

[Herfried K. Wagner [MVP]]

For a new programer, what would be the benefit of learning VB.NET over C#?

<http://www.deja.com>

SCNR

 

[Scott M.]

You may hear this and that about one language being better than the other,
but it really does come down to choice. I think William hit it right on the
head.

 

[Jay B. Harlow [MVP - Outlook]]

Robert,
As the others have suggested. For a new programmer learning .NET I would
recommend learning the Framework itself. Plus learning solid OOP theory.

Of course you will need the basics of either VB.NET or C# to learn the
Framework, however I would concentrate on learning the framework, not the
specifics of either language.

Whether you should learn VB.NET or C# I would consider a personal choice. Do
you like the way C# reads or do you like the way VB.NET reads?

I would recommend you sit down with one of entry level books, such as "OOP
with Microsoft Visual Basic .NET and Microsoft Visual C# .NET - Step by
Step" by Robin A. Reynolds-Haertle and page through some of the chapters. If
the C# samples make more sense use it, if the VB.NET samples make more sense
use it. Note: Robin's book covers the How of OOP, however it does not really
cover the Why of OOP, I consider it a good second or third book for learning
..NET.

Ultimately I consider it worthwhile to at least be able to read both, as
there are enough samples in each that strictly knowing one is "not
enough"...

Hope this helps
Jay

 

[Cor]

Hi Robert,

For a new programer, what would be the benefit of learning VB.NET over C#?

Not that I am lazy but the answer is simple, nothing

Cor

 

[Robert]

Thanks for the feedback!

 

[Kenneth Lantrip]

Hi Robert,


Not that I am lazy but the answer is simple, nothing

Cor

I'm wondering then, how would one write in visual basic .net the
following from C#?...

x =>> 3

or..

x = x >> 3

if that is a valied C# command... I do not know becuase I don't have
it... I only have the Visual Basic .NET Standard.

But I've heard one can make the exact program from either... But what
is the VB.net way of the above?

Thanks.

 

[Cor]

Hi Kenneth,

I think this is a better answer than telling you

http://www.harding.edu/USER/fmccown/WWW/vbnet_csharp_comparison.html

Was this where you where looking for?

Cor

 

[Armin Zingler]

Hi Kenneth,

I think this is a better answer than telling you

http://www.harding.edu/USER/fmccown/WWW/vbnet_csharp_comparison.html

Was this where you where looking for?

....and this one:

http://msdn.microsoft.com/library/en-us/vsintro7/html/vxgrfLanguageEquivalents.asp

 

[Herfried K. Wagner [MVP]]

I'm wondering then, how would one write in visual basic .net the
following from C#?...

x =>> 3

or..

x = x >> 3

if that is a valied C# command... I do not know becuase I don't have
it... I only have the Visual Basic .NET Standard.

Bit shifting operators are included in VB.NET 2003. Nevertheless, there
were only rare situations (often ugly Windows API hacks) in which I
needed these operators.