Re: Which is better, C# or VB, and why?

Tech-Archive recommends: Fix windows errors by optimizing your registry


"lastusernameleft" <lastusernameleft@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:F481DA8A-B5C2-4962-AB11-C8E7F1C121C3@xxxxxxxxxxxxxxxx
> i've been researching this issue for a while and can't come to any
> conclusive
> answer, mostly it seems to be a preference over syntax, some saying c# is
> elegant while vb is clunky, or that c# is geeky while vb is more naturally
> legible. there dont seem to be many capabilities in one over the other, at
> least with whidbey, so basically, is there anything c# can do that vb
> can't?

Each language has a few, little things different. In 1.x VB has its
dynamically bound mode when option strict is off and has access to a few
little things like parameterized properties(I believe) while C# has support
for pointers, unsigned tyupes, and operator overloading.

In whidbey, VB added operator overloading and direct supprot for unsigned
types as well as some other niceties(like OrElse and AndAlso, IIRC), but the
languages actually diverged just a little bit moreso than they were. Both
got generics and partial types, but much of the VB effort went into things
like Edit&Continue(C# basically hopped on that bandwagon pretty late), the
My namespace, and the things I mentioned before while C# added a few little
thigns like anonymous methods that are close to closures and iterators.

I think anon methods are the only thing I'd consider an advantage. Iterators
are nice but IEnumerable\IEnumerator implemetnations are not *that* hard to
write manually. Out side of that I don't see much advantage except for
personal preference or in very specific circumstnaces(C# for pointer ridden,
native code or VB for rich COM work, office automation for example)


.