Dick said:
IMO, there never was a significant difference between the two -- and this
non-difference still is extant. C# allows you to write unsafe code (not
bad, just unsafe in terminology). VB does not.
As to speed differences, these are trivial, and it is possble to cherry-pick
and find some that performs better than the alternate using either.
Dick
--
Richard Grier, MVP
Hard & Software
Author of Visual Basic Programmer's Guide to Serial Communications, Fourth
Edition,
ISBN 1-890422-28-2 (391 pages, includes CD-ROM). July 2004, Revised March
2006.
See
www.hardandsoftware.net for details and contact information.
Well said. Anyone who tries to make a mountain out of the molehill of
difference between C# and VB.Net is being a silly zealot. Unless
you're doing some very close-to-the-metal stuff (in which case you
should be working in C++) C# and VB.Net are basically the same language
with slightly different syntaxes. There are a few gotchas that come
from some of the differences between default behaviours of the
languages (C#'s shorcircuiting vs. VB.Net's non-shortcircuiting
operators, for example) but generally they're the same thing. Really,
any programmer worth his salt who knows one language would be able to
pick up the other in two hours. This isn't like learning SQL, or LISP,
or any other language that runs on a completely different paradigm from
the C-family. VB.Net is C# with words instead of characters, and a few
minor gotcha-style differences.
To a newb, I'd suggest C# because of the better support, and
familiarity in comparison to most other languages you'll run into...
Plus, MS tends to give C# slightly-better support - VB.Net is usually a
few small language features behind (eg. XML DocStrings). But if you
already know VB, Pascal, VBA, or other "wordy" languages and enjoy them
- just use VB.Net.
