C# .NET versus VB .NET

[Daniel Bass]

I'm just getting into the .Net experience from a VC++ (6.0) background, and
am looking at the .Net languages.

Just wondering what the differences are, in your opinion, between C# and VB,
dispite the obvious syntax changes between the two where '}' is 'End Sub',
and the fact you can still have "modules" in VB, where as C# is toltally OO.
The .Net libraries that are exposed to both seem to be identical, so what
advangtages/disadvantages, would one have over the other?

Or are they just both for different people, coming from differing
programming background, doing essentially the same thing?

Thanks. =o)
Dan.

 

[Andreas =?ISO-8859-1?Q?M=FCller?=]

I'm just getting into the .Net experience from a VC++ (6.0)
background, and am looking at the .Net languages.

Just wondering what the differences are, in your opinion, between C#
and VB, dispite the obvious syntax changes between the two where '}'
is 'End Sub', and the fact you can still have "modules" in VB, where
as C# is toltally OO.

VB.NET is completely OO, too. (as completely as a language without
template support can be OO ;-) )

The .Net libraries that are exposed to both
seem to be identical, so what advangtages/disadvantages, would one
have over the other?

Or are they just both for different people, coming from differing
programming background, doing essentially the same thing?

Thanks. =o)
Dan.

Hi,

I recently made the transition from a C++ background to .NET. From my
experience, C# and VB.NET are completely interchangeable. One always has
a small nice gadget that the other doesn't have, but these are really
minor things. The erason for this is, that every .NET language is
compiled into the same "Common Language"

I personally started with VB.NET for a simple reason: The syntax is so
different to C++, that you don't get into C++ thinking, which a lot of
times can't be applied under .NET. However, as the syntax is very easy
and the IDE supports you extremely good, it enabled me to concentrate on
learning the .NET Framework and concepts

Currently I'm somehow drifting back to C#. This is mainly because there
are some things in C# are more easy to do. This is propably because it
is a new language and doesn't have as many legacy constructs and rules
as VB.

So bottom line is, its a personal decision what language to take. I
would recommend to start with one, but learn the other as well later on,
so you can decide from project to project which fits best.

HTH,
Andy

 

[Frank Oquendo]

Thus spake Andreas Müller:

I personally started with VB.NET for a simple reason: The syntax is so
different to C++, that you don't get into C++ thinking, which a lot of
times can't be applied under .NET.

Funny you should mention that. Coming from VB6, I switched to C# for
precisely the same reason. Using a totally new language forced me out of
my rut and allowed me to focus on the framework rather than the
language.